skilllisted

# Spec orchestrator A spec is a directory under `specs/<slug>/`. It exists for two reasons and neither is telling the model what to do: someone reviews the shape before the work lands, and the work outlives the conversation that started it. `.claude/rules/spec-workflow.md` owns the decision threshold, the artifact layout, and the lifecycle vocabulary. This skill is the procedure over them. Read [gates.md](gates.md) when a gate fires and [resume.md](resume.md) on a resume. ## Phase is derived, never stored There is no `phase:` field. Which phase the work is in is read off the tree: **The first row that matches**, checked top to bottom. Ordered most-advanced first so a spec with no `plan.md` — which the rule allows — still reads as `implement` once its commits exist, rather than as `specify` forever: | On disk | Phase | |---|---| | `wrapup.md` present | wrapup | | implementation commits tagged for this slug | implement | | `plan.md` present | plan | | `spec.md` present | specify | A stored phase is a second copy of a fact the directory already states, and it is the copy that goes stale the moment someone writes a file without updating it. Deriving costs one `ls` and cannot disagree with reality. The labels are **descriptive, not a state machine.** Revisit any of them at any time — a plan that implementation disproves sends the work back to plan, and that is the process working. What is enforced is the gates, not the order. ## Invocation | Argument | Mode | |---|---| |