speclisted

Dispatcher for the canonical decomposed workflow (AGENTS.md § The Workflow) — routes the first token of $ARGUMENTS to one of four subcommands: plan, critique, execute, or retro. Each is pointed at a .oh/tasks/<slug>/ folder (the universal interface) and is the same independently-runnable, fan-out-able node /ship-spec decomposes into. Full per-subcommand procedures live in references/{plan,critique,execute,retro}.md. Authority: AGENTS.md § The Workflow. TRIGGER when: a topic/plan/issue needs to become a buildable task folder, "plan <topic>", "scaffold the task for <issue>" -> plan; a planned .oh/tasks/<slug>/ folder needs adversarial review + a go/no-go decision, "critique <slug>", "vet the plan for <slug>" -> critique; an APPROVED .oh/tasks/<slug>/ folder needs building to a promotable PR, "execute <slug>", "build <slug>" -> execute; a build PASSed audit and its lessons should be captured, "retro the <slug> build", "capture lessons for <slug>" -> retro.
mifunedev/openharness · ★ 40 · AI & Automation · score 79

Install: claude install-skill mifunedev/openharness

# /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