domains / families / software-engineering / spec-coder

spec-coder

separate

Structured spec-first development workflow with multi-role expert review gates: clarify requirements, author spec documents (requirements/design/tasks), generate code from spec, verify with real tests, and iterate while keeping spec and code in sync. Use when user wants to build a feature or system with a spec-first approach, mentions "spec coding", "spec-driven development", or asks to write specs before coding.

When to use

• User mentions "spec coding", "spec-first", "spec-driven development"
• User asks to write specs / requirements / design docs before implementation
• User mentions phase keywords: "clarify requirements", "write a spec", "generate from spec"

When not to use

• pure bug fixes
• one-line config changes
• dependency updates
• tasks completable in < 15 minutes without design decisions

Skill page

Source