Common Document Template Structure
Story and ADR templates MUST follow a common base structure with type-specific extensions.
Common Base Structure:
- •YAML frontmatter with
stateandscorefields - •Document type heading (
# User Storyor# Architectural Design Record (ADR)) - •
## Titlesection - •
## Statussection - •
## Contextsection - •Type-specific sections
DO:
- •User Stories: Include Acceptance Criteria (Gherkin Given/When/Then), Definition of Done, optional Notes
- •ADRs: Include Decision, Alternatives Considered, Consequences (Positive/Negative/Neutral)
- •Follow template precedence when best practices conflict with common structure
DON'T:
- •Omit Status or Context sections from either template type
- •Use non-standard section ordering
- •Add duplicate sections from best practices that conflict with common structure
Rationale: Consistent structure reduces cognitive overhead and enables reliable CLI processing.