12. Template System

Scan: Graduated template sets (starter/standard/full), template_{type}.md naming, template index recommendation.

Decisions: D11

12.1 Graduated Template Sets

Templates live in how/templates/. Projects grow their template sets:

Starter set (every aDNA instance MUST include):

Template	Purpose
`template_session.md`	Session file with SITREP and next-session prompt sections
`template_mission.md`	Mission with objectives, acceptance criteria, objective list
`template_context.md`	Context library file with topic structure and token estimate

Standard set (SHOULD include for active multi-agent projects):

Template	Purpose
`template_coordination.md`	Cross-agent coordination note
`template_backlog.md`	Backlog idea with priority, effort, status
`template_adr.md`	Architecture Decision Record

Full set (MAY include per project domain):

Additional templates for domain-specific content types (customer, partner, model, dataset, etc.).

Templates MUST follow the naming pattern template_{type}.md.

Templates MUST include frontmatter with all required base fields (§7.2) plus type-specific fields pre-populated.

A template index (e.g., template_library.md in how/templates/) is RECOMMENDED for projects with 5 or more templates.