← ClaudeAtlas

spec-unitlisted

Write the spec file for one unit of a planned build. Reads the project's context files and build plan, asks the user about anything unit-specific that is undecided, and writes context/specs/NN-unit-name.md with goal, design, implementation, dependencies, and a verification checklist. Use this whenever the user says "write the spec for unit 3", "spec the next unit", "what's next to build", "plan the next feature", or wants to add a new feature to a project that already has a context/ folder. Run this before build-unit; it writes no code.
SrunLyheang/AI-Builder-Playbook · ★ 0 · Web & Frontend · score 72
Install: claude install-skill SrunLyheang/AI-Builder-Playbook
# Spec Unit Write the complete instruction set for one unit of the build, so the implementing agent has nothing to guess. A spec replaces the vague prompt. A vague spec gives vague code; a detailed one gives predictable code. Specs are written just before a unit is built, never all upfront, because each unit teaches something that changes the next. This is the second of three skills: `plan-app` produces the context files and build plan, `spec-unit` (this one) specifies one unit, and `build-unit` implements it. ## Ground rules - **Write no application code and install nothing.** The only output is one Markdown file in `context/specs/` and small updates to the progress tracker. - **One unit per run.** - **Decide nothing on the user's behalf.** A product or design decision that the context files do not settle is a question for the user. - **Never spec from a vague request.** See "Vague requests" below. ## Vague requests A request is vague when two developers could build different things from it: "add a dashboard", "make onboarding better", "add some AI", "let users share stuff". A spec written from that is a guess with headings. Every time the user's request or answer is vague, at any step, do all three before continuing: 1. **Say what is unclear**, in one line. 2. **Ask one sharper question** at a time (what the user clicks, what appears, what is stored, what happens on failure). 3. **Give your recommended answer with the reason**, tied to this project's co