spec-driven-docs 0.8.1

Spec-driven documentation: current specs, immutable decision records, and executable gates kept coherent for people and coding agents.
Documentation
---
digest-of: method/
last-synced: 2026-09-09
token-estimate: 580
---

# AGENTS

## Scope

The spec-driven documentation method: artifact ownership, placement, rules, decision records, agent context, format, lifecycle, traceability, procedures, operational documents, gates, and migration.

## How to use this shelf

Load this digest, then the one chapter that owns the question. Load `_docs/specs/` for changes to the canon itself. Do not read decision records unless the rationale is requested.

## Routing

| Question                          | Owner              |
| --------------------------------- | ------------------ |
| Artifact ownership and precedence | `model.md`         |
| Placement and domains             | `placement.md`     |
| Spec shape                        | `specs.md`         |
| Requirement grammar and IDs       | `rules.md`         |
| Decision-record lifecycle         | `decisions.md`     |
| Agent loading and budgets         | `agent-context.md` |
| Markdown and size budgets         | `format.md`        |
| Living-document lifecycle         | `lifecycle.md`     |
| Executable enforcement            | `gates.md`         |
| Spec-to-code traceability         | `spec-to-code.md`  |
| Procedures                        | `procedures.md`    |
| Operational documents             | `operational.md`   |
| Migrating an existing corpus      | `migration.md`     |
| Writing prose                     | `writing-style.md` |
| Review                            | `checklist.md`     |

Stable copies live under `../templates/`. Installation and ownership live under `../instance/`.

## Maintenance

- Keep this digest a router.
- Update `last-synced` when routing changes.
- The owning chapter wins on disagreement.