← ClaudeAtlas

rjv-spec-drivenlisted

Use BEFORE coding any real feature, architecture/foundation, public SDK/API/contract, state machine, durable-data change, multi-app/multi-actor journey, embedded feature, or branch with multiple implementation/review slices—even when the user never says 'spec'. Also use for acceptance criteria, requirements docs, glossary/ubiquitous language, ADRs, reviewing a diff against requirements, or answering what behavior is live. Create `_docs/features/{area}/spec.md` with permanent criterion IDs and one test per criterion; bind WORK, handoff, REVIEW, and QA to those IDs. No criterion is met without a passing mapped test, and no QA/ship approval is allowed while any criterion is GAP. Compose with `rjv-work-plan`; high-stakes or multi-agent work also requires `rjv-gated-build`.
rjvim/ai-skills · ★ 0 · Testing & QA · score 61
Install: claude install-skill rjvim/ai-skills
# Spec-driven: durable truth and acceptance criteria The durable half of the workflow. `rjv-work-plan` holds volatile branch state and is always on; this skill owns what is permanently true: the spec (as testable acceptance criteria), the glossary, and the decision records. `rjv-gated-build` layers on top of both for gated work. **There is no prose "how it works today" doc**, because it rots. Durable truth is (1) the acceptance-criteria spec, which carries its own test-backed status, (2) the glossary, (3) ADRs. "What's true today" = code + tests + these three. ## Three durable artifacts, each with a bundled format | Artifact | Home | Format | Holds | |---|---|---|---| | **Spec** | `_docs/features/<area>/spec.md` | [SPEC-FORMAT.md](./SPEC-FORMAT.md) | requirements AS acceptance criteria (`U1`, `U2`…), 1 criterion = 1 test, per-group status | | **Glossary** | `CONTEXT.md` / `<area>/CONTEXT.md` | [CONTEXT-FORMAT.md](./CONTEXT-FORMAT.md) | ubiquitous language, terms + `_Avoid_` | | **ADRs** | `docs/adr/NNNN-*.md` | [ADR-FORMAT.md](./ADR-FORMAT.md) | decisions + why, immutable after first commit | Read the format file when authoring that artifact. **Produce exactly the structure in the format file:** fill the template, match the worked example's shape, and keep its sections and ID numbering as given. ## Mandatory activation gate `rjv-work-plan` owns the classification. Its Build-mode gate holds the one list of triggers and records the answer as `Build mode` in the branch pl