Skip to content

Workflows overview

A workflow is a multi-step skill that drives a phase of the product lifecycle. This section documents the ones a developer or PO invokes directly. For the full per-command catalog (including internal helpers), see the Skills reference.

You don't have to remember these commands

The always-on router rule makes Claude the dispatcher: describe what you want in plain language ("I have an app idea", "fix #123", "what should I do next?") and Claude routes to the matching skill itself, announcing the choice in one line. The /steer:* forms below are the explicit way to invoke a workflow — handy when you already know the one you want — not something you must memorize. Decision gates (creating issues, approving a spec, pushing a PR, deploying) still pause for a human regardless of how the skill was reached.

flowchart LR
    subgraph Setup
      setup["/steer:setup<br/>detect & route"]
      init["/steer:init<br/>new repo"]
      adopt["/steer:adopt<br/>existing app"]
      setup --> init & adopt
    end
    subgraph Build loop
      issues["/steer:issues"]
      spec["/steer:spec"]
      work["/steer:work"]
    end
    subgraph Steady state
      sync["/steer:sync"]
      drift["/steer:audit spec"]
      audit["/steer:audit"]
    end
    Setup --> issues --> spec --> work --> drift
    work --> sync

Setup (one-time)

Skill Use when
/steer:setup The front door — detects the repo state and routes to the right path below. Start here.
/steer:init (via setup) A new repo with no /spec spine — installs the bundled scaffold + spine.
/steer:adopt (via setup) An existing app with working code but no spine.

Build loop

Skill Use when
/steer:issues Drive an idea from capture → draft spec → decomposed work.
/steer:spec Think a feature through and shape/approve acceptance criteria.
/steer:work Start, resume, or finish a specific issue. Add --reviewed to run it through a review-gated loop (plan → plan-gate review → implement → /code-review → bounded fix) — vetted, not first-draft.
/steer:build A non-developer wants to build or prototype an idea.

Steady state

Skill Use when
/steer:sync (via /steer:setup) After a plugin release — apply migrations, reconcile spine + scaffold.
/steer:audit Periodic read-only pass: code for whole-repo standards-conformance health, spec to audit the built app against its tracker specs, all for both.
/steer:next "What should I do next?" across the whole workspace (read-only).
/steer:roadmap Generate a release-milestone timeline from the /spec spine (viewable as a GitHub Projects v2 roadmap).