← ClaudeAtlas

build-unitlisted

Implement one unit of a planned build exactly as its spec file says, verify it against the spec's checklist, and update the progress tracker. Use this whenever the user says "build unit 3", "implement the next unit", "implement context/specs/04-...", "build the spec", "fix unit 3, it doesn't match the spec", "unit 3 is done, close it out", or asks for changes or extra features while a unit is being built, in a project that has a context/ folder with spec files. Requires a spec written by spec-unit; if none exists, run that first.
SrunLyheang/AI-Builder-Playbook · ★ 0 · Web & Frontend · score 72
Install: claude install-skill SrunLyheang/AI-Builder-Playbook
# Build Unit Implement one unit from its spec: no more and no less. The spec and the context files already contain the decisions. This skill's job is to carry them out faithfully. Extra features, tidy-ups, and "while I'm here" changes are how a build drifts away from its plan, so they are out even when they look helpful. This is the third of three skills: `plan-app` plans, `spec-unit` specifies one unit, and `build-unit` (this one) implements it. It runs in one of three modes depending on what the user asks for: implement, correct, or close. ## Before anything: load context Read the entry-point file (`CLAUDE.md` or `AGENTS.md`), every context file it lists, and the spec for the unit in `context/specs/`. Stop and tell the user if: - there is no spec file for the unit (run `spec-unit` first) - a unit this one depends on is not marked complete in `context/progress-tracker.md` - the spec conflicts with an invariant in `architecture.md` If the user did not name a unit, use the one listed under Next Up in the progress tracker and confirm it. ## Vague requests A request is vague when it could be carried out in more than one way: "make it look nicer", "it feels off", "fix the form", "add the usual validation", "clean this up". Acting on one means guessing, and a wrong guess costs a rebuild. Every time the user's request is vague, in any mode, do all three before changing code: 1. **Say what is unclear**, in one line. 2. **Ask one sharper question** at a time (which ele