spec

# /spec — canonical workflow dispatcher `/spec <subcommand> [args]` is the single entry point to the decomposed `spec-*` workflow nodes. The first whitespace-delimited token of `$ARGUMENTS` selects the subcommand; everything after it is that subcommand's own argument string. Each subcommand's full procedure lives in a reference doc under `references/` — read that doc and follow it as the authoritative instructions. This is the decomposed form of `/ship-spec`. `/ship-spec` remains the all-in-one composer that runs the same `plan → critique → execute → retro` pipeline in one invocation (what `/autopilot` drives) and is the single source of the protected build mechanics each `/spec` node composes. The dispatcher is the same pipeline split so each node can be run independently or fanned out at scale via `/delegate`. ## Subcommands | Subcommand | Arg shape | Purpose | Procedure | |---|---|---|---| | `plan` | `<topic> [--plan <path>] [--issue <N>] [--slug <slug>] [--prefix <type>] [--repo <o/n>] [--base <branch>]` | Turn a topic/plan/issue into a fully-scaffolded `.oh/tasks/<slug>/` four-file folder | `references/plan.md` | | `critique` | `<slug> [--auto]` | Run the two adversarial critics (`/critique`) + the commitment gate (`/approve`); the `plan ⇄ critique` loop | `references/critique.md` | | `execute` | `<slug> [--pr <N>] [--repo <o/n>] [--remote <name>] [--base <branch>]` | `build ⇄ audit → spec-retro → improve → groom` to a ready PR, stopping at the human merge gate | `re...