What problem does it solve? Turning a written specification into working code often drifts: tasks get skipped, invariants get violated, and test failures get patched blindly without fixing the root cause. This Skill enforces a disciplined single-threaded workflow that implements a SPEC.md file task by task, tracks status directly in the spec, and routes every failure through a root-cause analysis before retrying. ## Core Features & Use Cases - Spec-driven task execution: Parses §T task rows from SPEC.md and implements them individually (build §T.3), the next pending one (build --next), or all pending tasks in order. - Plan gating: Before writing code, it cites every applicable §V invariant and §I interface, lists files and tests to touch, and waits for user approval. - Failure backpropagation: On test or build failure, it classifies the cause as a code bug, a spec error, or an unspecified edge case, and updates the spec's §V invariants and §B memory before resuming. - Use Case: A developer maintains a living SPEC.md for a project and asks the assistant to "build --next"; the skill flips the task status, implements it, runs the verification command, commits with invariant citations, and moves on. ## Quick Start Ask the assistant to run the build skill with "build --next" to implement the next pending task from SPEC.md.