What problem does it solve? Keeping a project specification accurate as code evolves is hard: specs drift from implementation, bugs get fixed without updating invariants, and ad-hoc edits break document structure. This Skill makes SPEC.md the single source of truth by acting as its sole mutator, enforcing a strict caveman-encoded format with numbered sections. ## Core Features & Use Cases - Four dispatch modes: NEW (idea to spec), DISTILL (reverse-engineer a spec from existing code), BACKPROP (record bugs into section B and derive new invariants in section V), and AMEND (targeted edits to named sections like §V.3 or §T). - Structured spec format: Maintains sections §G (goal), §C (constraints), §I (interfaces), §V (invariants), §T (task pipe table), and §B (bug log) with monotonic numbering that is never reused. - Use Case: After fixing a recurring authentication bug, invoke the skill with "bug: session token not refreshed" to append a §B row, draft a new invariant in §V, and update affected §T tasks — all shown as a diff before applying. ## Quick Start Ask the assistant to write the spec for your project idea, or say "bug: <description>" to backprop a bug into the existing SPEC.md.