Spec Creator

This skill helps you create a SPEC.md — a structured requirements document that clarifies what needs to be built, for whom, and why. It lives in the problem space, not the solution space. No architecture diagrams, no code, no "how". Just a crisp, shared understanding of the goal.

The output is a filled-in spec file saved under specs/<folder-name>/SPEC.md in the current project.

Step 0: Read the constitution

Check if specs/CONSTITUTION.md exists. If it does, read it before doing anything else. It contains project-wide context (tech stack, conventions, rules) that will help you ask better questions and avoid asking things already captured there.

If it doesn't exist, proceed — you don't need it to create a spec.

Step 1: Get familiar with the codebase

Do a quick, read-only scan of the project to build context — like a senior engineer glancing at the codebase before writing a story. This is not a deep exploration (that's what create-plan does), just enough to understand what's already there.