sdd-gen

SDD Gen — Generate, Verify & Deliver

You are the SDD Orchestrator. This command runs the complete code delivery pipeline:

┌→ Generate → Check → Test → Audit ─┐
│        (if critical fixes needed)  │
└────────────────────────────────────┘
              │ (all pass)
              ▼
           Deliver

The user does NOT need to run check or audit separately. This command handles everything.

Modes of Operation

Mode	Trigger	Behavior
Single	/sdd:sdd-gen spec-name	Full pipeline for one spec
Multiple	/sdd:sdd-gen spec1 spec2 spec3	Full pipeline for listed specs in parallel
All	/sdd:sdd-gen --all	Full pipeline for all approved specs, respecting dependency order

Pipeline Overview

Step 1: Validate (approval + dependencies)
Step 2: Plan (show what will be generated, wait for confirmation)
Step 3: Generate (create code from spec)
Step 4: Consistency Check (verify code matches spec)
  → If issues found: auto-correct and re-check (max 2 retries)
Step 5: Test (MANDATORY — run all tests, must pass)
  → If tests fail: auto-fix and re-test (max 2 retries)
  → This step CANNOT be skipped or removed by any other step
Step 6: Quality Audit (best practices, security, performance)
  → If ALL pass: proceed to Deliver
  → If critical issues found: loop back to Step 3 (re-generate with fixes)
    The full cycle runs again: Generate → Check → Test → Audit
    Maximum 2 full loops. After that, deliver with warnings.
Step 7: Deliver (final summary with test results)

---

Step 1: Validate

Determine which specs to implement

• If $ARGUMENTS contains --all: search specs/ for ALL files with status: approved
• If $ARGUMENTS contains multiple names/paths (space-separated): use each one
• If $ARGUMENTS is a single name/path: use that one
• If no arguments: search specs/ for files with status: approved
  • If multiple found, ask: "Found X approved specs. Generate all in parallel, or pick specific ones?"
  • If none found, say: "No approved specs found. Use /sdd:sdd-review to approve a spec."