skills.rest
Eyhenij
EyhenijCOMMUNITY
Explore all skills by this author →
GitHub

spec-driven

Defines documentation layers and binding rules for specs, laws, rules, and patterns.

1|Updated Jan 14, 2024
Search Tags:#documentation#spec-driven#audit#governance#rules#laws#agent-kit
One-click install
npx skills add https://github.com/Eyhenij/rt-tools --skill spec-driven-eyhenij
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: spec-driven
Source: https://github.com/Eyhenij/rt-tools/tree/main/.claude/skills/spec-driven
Command: npx skills add https://github.com/Eyhenij/rt-tools --skill spec-driven-eyhenij

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? It keeps project documentation consistent by defining how laws, rules, patterns, and domain specs relate to each other, how every statement binds to a place in code, and how scenarios stay linked to their tests. ## Core Features & Use Cases - Layered documentation model: Distinguishes laws (portable statements), rules (project bindings), patterns (ready-made techniques), and domain specs, with strict linking rules between them. - Binding and audit rules: Requires every article to be bound to a code anchor checked both ways, scenario numbers issued once and never reused, and spec sections fixed in advance. - Use Case: When editing a domain spec or creating a new rule in a repository using the rt-kit documentation system, load this rule to learn the mandatory sections, the companion implementation.md format, and the checks that will refuse non-compliant edits. ## Quick Start Load the spec-driven rule before editing any spec, law, or skill file so the documentation layers and binding requirements are applied correctly.

Frequently Asked Questions about spec-driven

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I structure project documentation with laws, rules, and patterns?▼

Use three layers: laws in docs/constitution state what must be true without naming files, rules in .claude/skills bind a law to the project, and patterns provide ready-made code under a rule. Domain specs in docs/specs declare the laws they apply.

How do I bind a documentation statement to code?▼

Write the binding in the companion implementation.md next to the rule, using a file:symbol anchor. The link is checked both ways by check-specs.mjs, and the first column must copy the article text verbatim, not retell it.

Can a skill exist without declaring a law?▼

Yes, a skill without kind: rule or kind: pattern stands outside the ladder and is legitimate for work-process topics like generators or showcases. Inventing a law just to fit the ladder is explicitly not allowed.

Why must scenario numbers never be reused?▼

A scenario number ties the scenario to its test, so reissuing it leaves old references pointing at new promises while tests stay green. New scenarios take the next free number and deleted numbers stay empty.

What are the limitations of the spec audit checks?▼

The checks verify section presence, anchors, prefixes, and scenario-test links, but not semantics: state table rows, duplicate-meaning scenarios, and companion-rule agreement pass green even when wrong. Those are held by reading and review.

Related Skills

Explore More Software Engineering Skills→
GarethJBGarethJB

speckit-constitution

Update project constitutions and sync dependent governance templates.

Community
Advanced
dceoydceoy
120

speckit-checklist

Generate a requirements-quality checklist with CHK IDs referencing spec sections.

Community
Advanced
ai-ecoverseai-ecoverse
28

skill-authoring

Create, edit, and validate SLICC agent skills with frontmatter and companion files.

Official
Intermediate
striderZAstriderZA
72

quick-design

Generate lightweight design specifications for small game changes with acceptance criteria.

Community
Intermediate