stickman/.opencode/skills/spec-pipeline/SKILL.md

name, description

name	description
spec-pipeline	Lean implementation loop: Architect -> Developer -> User Verification.

Execution Logic

1. Phase 1: Architecture (Optional for small edits)

   • @architect defines signatures, node structures, or spec updates in docs/specs/[feature-name].md.
   • STOP: Wait for user approval on design choices before invoking developer.

2. Phase 2: Implementation & Engine Validation

   • @developer updates code and scenes using targeted diffs/snippets.
   • @developer runs headless syntax verification (resolve <godot>/<project> per platform — see the "Command-line testing & debug playback" section of AGENTS.md): <godot> --headless --check-only --script "res://path/to/script.gd" --path "<project>"
   • If static check fails, @developer fixes the code immediately.
   • Visual/debug verification (optional): to actually watch a scene run and read print() debug output, launch the Sandbox Stage with --play --scene <path> from the command line (append --verbose for engine warnings) — see the "Command-line testing & debug playback" section of AGENTS.md. This is faster than relying on headless assertions alone for runtime/visual bugs.

3. 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.

4. Phase 4: Documentation (Triggered manually by user)

   • Only call @writer after the user confirms: "Feature verified and working."