document-driven-development
Use for repository-level documentation-first engineering when the user explicitly requests document-driven or spec-first work, a PRD or feature contract, canonical documentation ownership, docs-to-code drift repair, synchronized docs/code/tests, or requirement-to-evidence closure. Also use for consequential externally visible or persisted behavior changes that must update an existing contract. Do not use for ordinary coding with no contract impact, one-off prose or file-format editing, architecture briefs or ADRs, or comparative source research.
Pinned to revision bec4b860bb09, so it is the text this page describes rather than whatever the author pushed since.
Files
- skills/document-driven-development/SKILL.md
- skills/document-driven-development/evals/evals.json
- skills/document-driven-development/evals/fixtures/retry-drift/AGENTS.md
- skills/document-driven-development/evals/fixtures/retry-drift/RETRY_SPEC.md
- skills/document-driven-development/evals/fixtures/retry-drift/ROLLOUT_PLAN.md
- skills/document-driven-development/evals/fixtures/retry-drift/retry.schema.json
- skills/document-driven-development/evals/fixtures/retry-drift/retry.test.ts
- skills/document-driven-development/evals/fixtures/retry-drift/retry.ts
- skills/document-driven-development/references/working-model.md
Every link opens the file at its source, pinned to the revision this page describes.