What problem does it solve? Teams maintaining spec-driven documentation struggle to keep laws, rules, and patterns consistent: laws leak project paths, rules lose their binding to implementation anchors, and descriptions grow past the context budget. This Skill encodes the structure, section sets, and audit expectations for each documentation layer so edits stay compliant. ## Core Features & Use Cases - Layered authoring guidance: Defines what belongs in a law (docs/constitution/), a rule (.claude/skills/<rule>/SKILL.md), and a pattern (.claude/skills/<rule>-<what>/SKILL.md), including mandatory sections and header formats. - Binding and audit rules: Explains the implementation.md binding table, accepted verdicts for unbound statements, and how npm run check:specs validates the structure. - Description and compression discipline: Provides the 300-character description budget, the load-or-not question, and a worked example of compressing an article while moving detail to pitfalls. - Use Case: When adding a new coding rule under an existing law, load this Skill to get the exact SKILL.md header, the required sections, the binding table format, and the common misses that cause the spec audit to fail. ## Quick Start Ask the assistant to create a new rule under the delivery law in .claude/skills following the spec-driven pattern, including its header, sections, and binding table.
