---
name: spec-pipeline
description: "Lean implementation loop: Architect (Clarify -> Spec) -> Developer -> User Verification."
---

## Execution Logic

1. **Phase 1a: Architecture Proposal & Clarification**
   - `@architect` analyzes existing patterns, pitches 1–3 Godot best-practice ideas, and asks up to 3 clarification questions with `[Recommended]` options.
   - `@architect` stops without writing the spec file yet.

2. **Phase 1b: User Feedback & Spec Generation**
   - User approves, modifies, or selects choices from `@architect`'s proposal.
   - `@architect` writes the finalized specification to `specs/[feature-name].md` and logs decisions in `docs/tech_debt_and_optimizations.md`.
   - **STOP:** Wait for final user sign-off on the spec before invoking developer.

3. **Phase 2: Implementation & Engine Validation**
   - `@developer` updates code and scenes using targeted diffs/snippets based on `specs/[feature-name].md`.
   - `@developer` runs headless syntax verification:
     `& "C:\Godot4\Godot_v4.7.1-stable_win64_console.exe" --headless --check-only --script "res://path/to/script.gd" --path "C:\Godot4\project"`
   - If static check fails, `@developer` fixes the code immediately.

4. **Phase 3: User Hand-off (Stop)**
   - Present the changes to the user to test inside the Godot Editor.
   - Do NOT update READMEs or documentation yet.

5. **Phase 4: Documentation (Triggered manually by user)**
   - Only call `@writer` after the user confirms: _"Feature verified and working."_