Spec

This is what spec-driven development looks like when forced into a workflow. It walks you through four phases: understanding project context, asking clarifying questions in structured blocks, building the spec section by section with your approval at each step, then saving it as a numbered markdown file in specs/. The questioning phase is intentionally slow because vague specs produce improvised code. It refuses to write any implementation code, only the spec document. Model invocation is disabled, so it stays disciplined about not jumping ahead. Once the spec is saved as Draft, you review it, mark it Approved, then run a separate command to implement. If you tend to skip planning and regret it three days later, this forces the discipline you know you need.

Install to Claude Code

npx -y skills add klerith/fernando-skills --skill spec --agent claude-code