← ClaudeAtlas

buildlisted

Plan-then-execute impl vs SPEC.md. Triggers when user asks to build, implement, ∨ execute spec ∨ specific §T task. Phrasings: "build §T.<n>", "build --next", "implement next task", "run the build", "does the implementation run?", "is §T.<n> done?".
kborovik/pilot-skills · ★ 4 · Web & Frontend · score 70
Install: claude install-skill kborovik/pilot-skills
# build — implement spec Single-thread native plan→execute. You are main Claude. No swarm. ## LOAD 1. Read `SPEC.md`. If missing → tell user to invoke the spec skill first. Stop. 2. Parse invocation args: - `§T.n` → that task only - `--next` or empty → lowest-numbered row with status `.` - `--all` → every `.` row in §T order ## PLAN Native plan mode. For chosen task(s): 1. Cite every §V invariant that applies. Plan must respect all. 2. Cite every §I interface touched. Plan must preserve shape. 3. List files to create / edit. 4. List tests to add or update (one per invariant touched). 5. Name verification command (test, build, lint). Emit plan inline ∀ task — transparency, ⊥ wait-state — then proceed to EXECUTE. ## EXECUTE Per task in order (status flips `.` → `x` direct): 1. Edit code per plan. 2. Run verification command. 2'. On staged diff touching PUBLISHED, probe `.claude/check-extras.md` ∧ run audit recipes it ships; bail per recipe message ∀ surviving match, ⊥ commit until match-free. Probe ⊥ match → no-op. 3. **Pass** (verification exits 0 ∧ tests added per plan ∧ ⊥ §V regressed via full-suite re-run) → flip §T.n status `.` → `x`; auto-commit. Surface `/sdd:check` as Next-block item #1 per §V.<n> (cascade scan; ⊥ silent close). Next task. 4. **Fail** → invoke backprop skill. Do NOT retry blindly. Status stays `.`. ## FAIL → BACKPROP On test/build failure: 1. Read failure output. 2. Classify failure: (a) code bug → step 3, (b) spec wrong → step 4,