AgileFlow

/update

PreviousNext

Generate stakeholder progress report

/update

Generate high-level project updates for stakeholders, executives, or clients with metrics, progress, and risks.

Quick Start

/agileflow:update PERIOD=week AUDIENCE=exec

Parameters

ParameterRequiredDefaultDescription
PERIODNoweekTime frame: week, sprint, month, quarter, or custom
START_DATENo-For custom period (YYYY-MM-DD format)
END_DATENo-For custom period (YYYY-MM-DD format)
AUDIENCENoexecTarget audience: exec, client, team, or board
FORMATNomarkdownOutput format: email, markdown, slides, or pdf

Examples

Executive Weekly Update

/agileflow:update PERIOD=week AUDIENCE=exec FORMAT=email

Generates a concise one-page update for C-level executives with:

  • Executive summary and overall status
  • Key accomplishments
  • Critical blockers or risks
  • Velocity and metrics
  • No technical jargon

Client Bi-Weekly Report

/agileflow:update PERIOD=2weeks AUDIENCE=client FORMAT=markdown

Generates a feature-focused update for clients with:

  • What users can now do
  • Progress toward contract deliverables
  • Screenshots or demo references
  • Transparent issue communication
  • User-benefit language

Team Sprint Retrospective

/agileflow:update PERIOD=sprint AUDIENCE=team FORMAT=markdown

Generates a detailed update for the team with:

  • Architecture decisions and ADRs
  • Technical accomplishments
  • Celebration of wins
  • Retrospective insights
  • Action items

Custom Period Update

/agileflow:update PERIOD=custom START_DATE=2025-12-01 END_DATE=2025-12-15 AUDIENCE=board FORMAT=pdf

Output

The command generates a comprehensive update saved to:

docs/08-project/updates/<YYYYMMDD>-update.md

Update Structure

Executive Summary

  • 2-3 sentence overview
  • Key accomplishments
  • Critical issues or risks
  • Overall status (On Track / At Risk / Blocked)

Progress This Period

  • Stories completed with counts
  • Epics progress percentages
  • Milestones reached

Upcoming Priorities

  • Next sprint focus areas
  • Upcoming milestones with dates

Metrics & Trends

  • Velocity (stories/week)
  • Completion rate percentage
  • Quality metrics (test coverage, bugs)
  • Trends (improving/declining)

Blockers & Risks

  • Current blockers with owners
  • Risk mitigation strategies
  • Status of each item

Decisions Made

  • Recent Architecture Decision Records (ADRs)
  • Rationale for key choices

Team Updates (if applicable)

  • Team capacity changes
  • Notable accomplishments
  • Morale indicators

Data Sources

The command aggregates data from 10 sources:

  1. docs/09-agents/status.json - Story status snapshots
  2. docs/05-epics/*.md - Epic progress and completion
  3. docs/06-stories//US-*.md** - Story details and completion
  4. docs/08-project/backlog.md - Backlog items
  5. docs/08-project/roadmap.md - Roadmap milestones
  6. docs/08-project/milestones.md - Milestone targets
  7. docs/08-project/risks.md - Risk register
  8. Git history - Commits and merged PRs
  9. docs/09-agents/bus/log.jsonl - Activity and events
  10. docs/03-decisions/adr-*.md - Recent decisions

Audience Customization

Executive (C-Level)

  • Very high-level overview
  • Business impact focus
  • Metrics and ROI
  • Risks highlighted early
  • Maximum 1 page

Client

  • Feature-focused language
  • User benefits emphasized
  • Transparent about issues
  • Screenshots/demo links included
  • Progress toward contract deliverables

Team

  • More technical detail included
  • Architecture decisions included
  • Celebration of wins
  • Retrospective insights
  • Action items for next period

Board

  • Strategic overview
  • Financial implications
  • Competitive positioning
  • Long-term roadmap
  • Risk assessment

Workflow

  1. Determine time period (default: this week)
  2. Collect data from all 10 sources
  3. Calculate metrics and trends
  4. Identify completed work and blockers
  5. Format for target audience
  6. Preview update in markdown
  7. Ask: "Send update? (YES/NO/EDIT)"
  8. If YES: Save to docs/08-project/updates/ and optionally email stakeholders

Use When

  • Weekly team syncs - Regular cadence updates
  • Executive presentations - Monthly/quarterly reporting
  • Client communication - Contractual progress updates
  • Sprint retrospectives - Team-focused learnings
  • Board meetings - Strategic alignment updates
  • Risk escalation - Highlighting blockers early

Integration

Link to epics and stories for additional detail. Reference ADRs for architectural context. Include GitHub PR links where relevant.

  • /metrics - Detailed project metrics and analysis
  • /retro - Sprint retrospective with Start/Stop/Continue format
  • /babysit - Monitor progress and suggest updates
  • /velocity - Track team velocity trends