Experimental (mattpocock/skills wayfinder port, MIT). Charts a foggy effort as a shared Linear decision map, resolves its decision tickets across bounded sessions, and hands one graduated effort to /belt:requirements. Upstream of /belt:feature-dev; one run graduates exactly one effort.
Runs the shared build stage: TDD implementation from the plan document's task list and two-agent code review with autonomous triage. Use standalone with an existing plan.md/fix-plan.md, or composed as the build stage of /belt:feature-dev and /belt:bug-fix. QA runs as its own stage (/belt:qa) after build; integration happens at the orchestrator's integrate phase.
Runs the feature design stage: goal-sheet intake (/belt:goal) followed by a design document (architecture + key decisions) reviewed by belt:spec-reviewer. Use standalone for design-only work, or composed as the first stage of /belt:feature-dev. Task breakdown lives in the plan stage (/belt:plan), not here. --codex enables adversarial spec review.
Runs the bug diagnosis stage: root-cause analysis with a failing reproduction test and reproduction scenarios, fix planning, and adversarial plan review. Use standalone for diagnosis-only work, or composed as the upstream stage of /belt:bug-fix. --codex enables adversarial plan review.
Quality-gated feature pipeline from ticket to integration: goal-sheet intake, design document with spec review, implementation plan with QA scenarios, context-reset checkpoint, TDD implementation, autonomous code review, mandatory QA with human-readable evidence (screenshots / transcripts), and integration with evidence publishing. Accepts a Linear id, URL, free text, or a requirements.md path. --codex enables adversarial review.
Runs the implementation planning stage: writes plan.md (test strategy + task list) and scenarios.yml (QA replay scenarios) from an approved design.md, then reviews the plan via belt:spec-reviewer. Use standalone when a design already exists, or composed between the design and build stages of /belt:feature-dev. --codex enables adversarial plan review.
Interview-driven requirements definition. Resolves a Linear ticket, URL, or free-text request, investigates the codebase, asks only human-decidable questions in dependency-ordered rounds until the frontier is empty, and writes docs/requirements/<YYYY-MM-DD-topic>/requirements.md reviewed by belt:spec-reviewer. The result feeds /belt:feature-dev as input.
General-purpose documentation writing. Takes a topic (feature, module, or theme), investigates the code, and creates or updates documents under docs/ following the repository's existing documentation conventions. Use for architecture overviews, usage guides, and reference pages.