AgileFlow

/template

PreviousNext

Create and manage custom document templates

/template

Create, manage, and use custom templates for standardizing documentation across your project. Build templates for stories, meetings, incident reports, and more.

Quick Start

# List all available templates
/agileflow:template
 
# Create a new custom template
/agileflow:template ACTION=create TYPE=custom NAME=meeting-notes
 
# Use a template to generate a document
/agileflow:template ACTION=use TYPE=custom NAME=meeting-notes

Parameters

ParameterRequiredDefaultDescription
ACTIONNolistOperation: list, create, edit, or use
TYPEFor create/edit/use-Template type: story, epic, adr, custom, etc.
NAMEFor create/edit/use-Template name (e.g., meeting-notes)
PATHOptionalautoCustom path to save template

Examples

List Available Templates

/agileflow:template

Shows all built-in and custom templates:

# Available Templates
 
## Built-in Templates (docs/00-meta/templates/)
- story-template.md - User stories
- epic-template.md - Epics
- adr-template.md - Architecture Decision Records
- agent-profile-template.md - Agent profiles
- comms-note-template.md - Handoff notes
- research-template.md - Research notes
- README-template.md - Folder READMEs
 
## Custom Templates (docs/00-meta/templates/custom/)
- meeting-notes.md (created 2025-10-15)
- incident-report.md (created 2025-10-10)
- sprint-retro.md (created 2025-10-01)
 
Usage: /agileflow:template ACTION=use TYPE=custom NAME=meeting-notes

Create a Meeting Notes Template

/agileflow:template ACTION=create TYPE=custom NAME=meeting-notes

Provides a template builder interface:

Creating new template: meeting-notes
 
Template content:
 
---
title: {{TITLE}}
date: {{DATE}}
attendees: {{ATTENDEES}}
---
 
# {{TITLE}}
 
**Date**: {{DATE}}
**Attendees**: {{ATTENDEES}}
 
## Agenda
1.
2.
3.
 
## Notes
 
### Topic 1
 
 
### Topic 2
 
 
## Action Items
- [ ] Task 1 (Owner: {{OWNER}}, Due: {{DUE_DATE}})
- [ ] Task 2
 
## Decisions Made
-
 
## Next Meeting
**Date**:
**Topics**:
 
---
 
Save to: docs/00-meta/templates/custom/meeting-notes.md
Proceed? (YES/NO)

Create an Incident Report Template

/agileflow:template ACTION=create TYPE=custom NAME=incident-report

Define an incident report template:

---
template: incident-report
version: 1.0
---
 
# Incident Report: {{TITLE}}
 
**ID**: INC-{{INCIDENT_ID}}
**Date**: {{DATE}}
**Severity**: {{SEVERITY}}
**Status**: {{STATUS}}
**Reporter**: {{REPORTER}}
 
## Summary
{{SUMMARY}}
 
## Timeline
 
| Time | Event |
|------|-------|
| {{TIME_1}} | {{EVENT_1}} |
| {{TIME_2}} | {{EVENT_2}} |
| {{TIME_3}} | {{EVENT_3}} |
 
## Impact
 
**Users Affected**: {{USERS_AFFECTED}}
**Duration**: {{DURATION}}
**Services**: {{SERVICES}}
 
## Root Cause
 
{{ROOT_CAUSE}}
 
## Resolution
 
{{RESOLUTION}}
 
## Prevention
 
### Immediate Actions
- [ ] {{ACTION_1}}
- [ ] {{ACTION_2}}
 
### Long-term Actions
- [ ] {{ACTION_3}} (Story: US-XXXX)
- [ ] {{ACTION_4}} (Story: US-XXXX)
 
**Post-Incident Review**: {{PIR_DATE}}

Create a Sprint Retrospective Template

/agileflow:template ACTION=create TYPE=custom NAME=sprint-retro

Define a sprint retrospective template with metrics:

# Sprint {{SPRINT_NUMBER}} Retrospective
 
**Dates**: {{START_DATE}} to {{END_DATE}}
**Team**: {{TEAM}}
**Facilitator**: {{FACILITATOR}}
 
## Sprint Goals
 
### Planned
{{GOALS_PLANNED}}
 
### Achieved
{{GOALS_ACHIEVED}}
 
## Metrics
 
| Metric | Target | Actual | Status |
|--------|--------|--------|--------|
| Stories Completed | {{TARGET_STORIES}} | {{ACTUAL_STORIES}} | {{STATUS}} |
| Velocity | {{TARGET_VELOCITY}} | {{ACTUAL_VELOCITY}} | {{STATUS}} |
| Test Coverage | {{TARGET_COVERAGE}}% | {{ACTUAL_COVERAGE}}% | {{STATUS}} |
| Bugs | <{{MAX_BUGS}} | {{ACTUAL_BUGS}} | {{STATUS}} |
 
## What Went Well? 🎉
 
1.
2.
3.
 
## What Didn't Go Well? 😞
 
1.
2.
3.
 
## What Should We Try? 💡
 
1.
2.
3.
 
## Action Items
 
- [ ] {{ACTION_1}} (Owner: {{OWNER_1}}, Due: {{DUE_1}})
- [ ] {{ACTION_2}} (Owner: {{OWNER_2}}, Due: {{DUE_2}})
- [ ] {{ACTION_3}} (Owner: {{OWNER_3}}, Due: {{DUE_3}})
 
## Shoutouts 🙌
 
-
 
**Next Retrospective**: {{NEXT_RETRO_DATE}}

Use a Template to Generate a Document

/agileflow:template ACTION=use TYPE=custom NAME=meeting-notes

Prompts for template variables and generates the document:

Using template: meeting-notes
 
Fill in template variables:
 
TITLE: Weekly Team Sync
ATTENDEES: Alice, Bob, Carol, DevOps Team
OWNER: Alice
DUE_DATE: 2025-12-31
 
Generated document preview:
 
---
title: Weekly Team Sync
date: 2025-12-24
attendees: Alice, Bob, Carol, DevOps Team
---
 
# Weekly Team Sync
 
**Date**: 2025-12-24
**Attendees**: Alice, Bob, Carol, DevOps Team
 
## Agenda
1.
2.
3.
 
[...preview continues...]
 
Save to: docs/08-project/meetings/2025-12-24-weekly-sync.md
Proceed? (YES/NO)

Edit an Existing Template

/agileflow:template ACTION=edit TYPE=custom NAME=meeting-notes

Shows the current template and prompts for edits with diff preview.

Template Syntax

Variable Format

Templates use double curly braces for variables:

# {{TITLE}}
 
**Created by**: {{AUTHOR}}
**Date**: {{DATE}}
**Status**: {{STATUS}}

Built-in Variables

Available in all templates:

VariableExampleDescription
{{DATE}}2025-12-24Current date (YYYY-MM-DD)
{{DATETIME}}2025-12-24T10:30:00ZISO 8601 datetime
{{USER}}aliceCurrent git user
{{YEAR}}2025Current year

Story Template Variables

For story-specific templates:

{{STORY_ID}} - Story identifier (US-0042)
{{EPIC_ID}} - Parent epic (EP-0001)
{{OWNER}} - Story owner/assignee
{{ESTIMATE}} - Story point estimate
{{AC}} - Acceptance criteria
{{DEPENDENCIES}} - Dependencies on other stories

ADR Template Variables

For architecture decision records:

{{NUMBER}} - ADR number (0001, 0042)
{{STATUS}} - Decision status (proposed, accepted, superseded)
{{CONTEXT}} - Driving factors
{{DECISION}} - The decision made
{{CONSEQUENCES}} - Trade-offs and impacts

Built-in Templates

AgileFlow includes default templates you can view and customize:

TemplatePurposeLocation
story-template.mdUser story formatdocs/00-meta/templates/story-template.md
epic-template.mdEpic definitiondocs/00-meta/templates/epic-template.md
adr-template.mdArchitecture decisionsdocs/00-meta/templates/adr-template.md
agent-profile-template.mdAgent documentationdocs/00-meta/templates/agent-profile-template.md
comms-note-template.mdHandoff notesdocs/00-meta/templates/comms-note-template.md
research-template.mdResearch findingsdocs/00-meta/templates/research-template.md
README-template.mdFolder READMEsdocs/00-meta/templates/README-template.md

You can override any built-in template by creating a custom version with the same name.

Best Practices

When to Create Templates

Create a template when:

  • A document type is created multiple times
  • A specific structure should be followed consistently
  • Certain fields should always be included

Template Naming

Use descriptive, kebab-case names:

Good:
- meeting-notes
- sprint-retrospective
- incident-report
- design-proposal
 
Avoid:
- template1
- doc
- new-file

Variable Naming

Use UPPERCASE_WITH_UNDERSCORES:

Good:
{{STORY_ID}}, {{OWNER}}, {{DUE_DATE}}
 
Avoid:
{{story_id}}, {{owner}}, {{due-date}}, {{Author}}

Documentation

Add descriptions to custom templates:

---
template: incident-report
version: 1.0
description: Post-incident documentation for service outages
author: DevOps Team
created: 2025-10-10
---

Template Management

Template Registry

Custom templates are tracked in docs/00-meta/templates/registry.json:

{
  "templates": [
    {
      "name": "meeting-notes",
      "type": "custom",
      "path": "docs/00-meta/templates/custom/meeting-notes.md",
      "created": "2025-10-15",
      "author": "Alice",
      "description": "Weekly team meeting notes",
      "variables": ["TITLE", "DATE", "ATTENDEES", "OWNER"]
    },
    {
      "name": "incident-report",
      "type": "custom",
      "path": "docs/00-meta/templates/custom/incident-report.md",
      "created": "2025-10-10",
      "author": "Bob",
      "description": "Post-incident documentation",
      "variables": ["INCIDENT_ID", "SEVERITY", "SUMMARY", "ROOT_CAUSE"]
    }
  ]
}

Team Sharing

Templates in docs/00-meta/templates/custom/ are committed to git, so:

  • All team members use the same templates
  • Templates are versioned with code
  • Template changes are reviewed in PRs
  • /adr - Create architecture decisions (uses adr-template.md)
  • /story-new - Create user stories (uses story-template.md)
  • /epic-new - Create epics (uses epic-template.md)
  • /research - Create research notes (uses research-template.md)