noddde

Internal procedure for the Auditor agent. Use /spec instead — it orchestrates the full pipeline. Runs Steps 5-6 (validate + update docs) with an independent context and an added coherence review. Produces an Audit Report.

Internal procedure for the Builder agent. Use /spec instead — it orchestrates the full pipeline. Combines Steps 2-4 (generate RED tests, implement code, run GREEN tests) into a single agent invocation. Produces a Build Report for the Auditor.

Spec-driven development orchestrator. The single entry point for all spec work: creating features, fixing bugs, evolving APIs. Drives the full 6-step pipeline (spec → RED tests → implement → GREEN tests → validate → update docs) autonomously, only pausing for developer approval at gate points. Use when asked to 'add a feature', 'implement', 'fix a bug', 'change the API', 'new spec', 'edit spec', or any development task.

Internal procedure for Step 3. Use /spec instead — it orchestrates the full pipeline. This skill contains detailed instructions for implementing a spec (code only, no test generation).

Internal procedure for Step 5. Use /spec instead — it orchestrates the full 6-step pipeline. This skill contains detailed instructions for validating implementation against spec.

Internal procedure for Step 6. Use /spec instead — it orchestrates the full pipeline. This skill contains detailed instructions for updating documentation pages after a spec is implemented or updated.

Internal procedure for Step 2. Use /spec instead — it orchestrates the full pipeline. This skill contains detailed instructions for generating vitest tests from a spec's Test Scenarios section.

Internal procedure for Step 4. Use /spec instead — it orchestrates the full pipeline. This skill contains detailed instructions for running tests and reporting RED/GREEN status.

Internal procedure for Step 1 (edit). Use /spec instead — it orchestrates the full pipeline. This skill contains detailed instructions for editing an existing spec with breaking change detection.

Internal procedure for Step 1 (new). Use /spec instead — it orchestrates the full pipeline. This skill contains detailed instructions for creating a new behavioral spec.

Show the implementation status of all specs in the project, including which pipeline step each is on. Use when asked "what's the status", "which specs are implemented", "what's left to do", "show progress", or for sprint planning.