spec
Spec
Once a plan has survived the interview, freeze it. This skill takes everything already in the conversation and the codebase and turns it into a spec you can hand to a reviewer or to your future self. It does NOT interview you. The interview already happened. This is the write-up.
Process
1. Understand the current state
Explore the repo if you have not already. Before exploring, load ../deep-interview/DOMAIN-AWARENESS.md and use the project's CONTEXT.md vocabulary throughout the spec. The spec should read in the project's own language, not generic boilerplate.
2. Sketch the modules
Map the major modules you will build or change to deliver this. Actively hunt for chances to extract deep modules: small interface, deep implementation, testable in isolation, rarely changing. See ../red-green/deep-modules.md for what that means.
Check two things with me before you write the spec:
- Do these modules match what I expected?
- Which modules do I want tests written for?