Standardized templates for consistent project artifacts.
Templates provide consistent structure for all project artifacts. They ensure nothing is forgotten and standardize communication.
| Template | Purpose | Created By |
|---|---|---|
story.md |
User story definition | SM |
epic.md |
Epic/feature grouping | SM |
ucv.md |
Use Case Verifications | UCV Writer |
adr.md |
Architecture Decision Record | Architect |
task.md |
Technical subtask | Developer |
handoff.md |
Session handoff | Any agent |
brief.md |
Product brief | Analyst |
prd.md |
Product Requirements Document | Analyst |
retrospective.md |
Sprint/epic retrospective | SM |
charter.md |
Exploratory test session | Exploratory QA |
templates/
├── README.md # This file
├── story.md # User story
├── epic.md # Epic/feature
├── ucv.md # Use Case Verifications
├── adr.md # Architecture Decision Record
├── task.md # Technical task
├── handoff.md # Session handoff
├── brief.md # Product brief
├── prd.md # PRD
├── retrospective.md # Retrospective (REX)
└── charter.md # Exploratory test charter
# Create a new story from template
"create story from template for user authentication"
# Create ADR from template
"create ADR for database selection"function createFromTemplate(
templateName: string,
variables: Record<string, string>
): string {
const template = readTemplate(templateName);
return interpolate(template, variables);
}Templates use {variable} syntax for interpolation:
# STORY-{story_id}: {title}
## Metadata
- **Epic**: EPIC-{epic_id}
- **Status**: {status}
- **Created**: {date}- Use templates consistently - Don't create ad-hoc formats
- Fill all required fields - Templates have required vs optional sections
- Keep templates updated - Evolve templates as needs change
- Version templates - Track template changes over time