spec-unitlisted
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