bmad-retrospective
bmad-code-org/bmad-method
Review finished epics against their evidence and produce sourced retrospectives with action items.
What is bmad-retrospective?
Analyzes completed epic folders by examining the epic file, ticket plans, diffs, and commits to generate a retrospective report with findings, action items, and acceptance decisions. Use this when you need to review a finished epic and document lessons learned.
- Examines epic files, ticket plans, diffs, and commits for evidence
- Produces retrospective reports with sourced findings
- Generates action items from the review
- Provides acceptance decisions based on evidence
- Supports headless mode for automation
- Integrates with BMad ticket tree structure
How to install bmad-retrospective
npx skills add https://github.com/bmad-code-org/bmad-method --skill bmad-retrospective- BMad project structure with ticket tree and epic folders
- Project root directory path
- Skill root directory path
- uv package manager installed
How to use bmad-retrospective
- 1.Ensure the epic you want to review is marked as finished in the ticket tree
- 2.Run the skill with the command: npx skills add https://github.com/bmad-code-org/bmad-method --skill bmad-retrospective
- 3.Execute the rendered workflow.md instruction that is printed to stdout
- 4.Review the generated retrospective report with findings and action items
- 5.Use the acceptance decision to sign off on the epic
Use cases
- Review a completed feature epic to identify what went well and what to improve
- Generate retrospective documentation for team learning after a major project milestone
- Audit ticket execution against original plans to find process gaps
- Produce acceptance sign-off for finished epics with evidence-based reasoning
- Automate retrospective generation in CI/CD workflows
- Engineering leads conducting post-project reviews
- Teams using BMad for structured ticket management
- Project managers documenting epic completion
- Development teams seeking to improve process
bmad-retrospective FAQ
The skill reviews the epic file, each ticket's plan, diffs showing code changes, and commit history to source all findings.
Yes, the skill supports -H/--headless mode for automated retrospective generation.
The skill will offer to run the bmad skill's setup first, installing BMad if needed, then retry the retrospective command.
The retrospective includes sourced findings, action items for future improvement, and an acceptance decision for the epic.
After running the skill, follow the one absolute workflow.md instruction printed to stdout to complete the retrospective process.
Full instructions (SKILL.md)
Source of truth, from bmad-code-org/bmad-method.
name: bmad-retrospective description: 'Review a finished epic folder in the ticket tree against the evidence it left behind — the epic file, each ticket plan, diffs, commits — and produce a retrospective with sourced findings, action items, and an acceptance decision. Use when the user says "run a retrospective" or "lets retro the epic [epic]". Supports -H/--headless'
Run the following command exactly once without changing the current working directory. Replace {project-root} with the absolute path to the project root and {skill-root} with the absolute path to this skill's directory:
uv run --no-cache "{project-root}/_bmad/scripts/render_skill.py" --project-root "{project-root}" --skill "{skill-root}"
- On success, read and follow the one absolute
workflow.mdinstruction printed to stdout. - If the script is not found, BMad is not set up here. Offer to run the
bmadskill's setup, installingbmadfirst if you do not have it (npx skills add bmad-code-org/BMAD-METHOD --skill bmad), then run the command above once more. - On any other failure (including
uvbeing unavailable), report the command output and HALT. Do not run any workflow source directly.
Related skills
More from bmad-code-org/bmad-method and the wider catalog.
bmad-review
Run multiple review lenses on code and documents to surface adversarial critique, edge cases, gaps, and structural issues.
bmad-spec
Distill any input into a machine-readable spec: kernel file plus companions for downstream BMad skills.
bmad-sprint-planning
Check planning readiness and generate sprint status from epics; validate and repair tracking files.
bmad-ux
Capture UX vision in DESIGN.md and EXPERIENCE.md documents via structured elicitation.
bmad-walkthrough
Guide structured human review of commits, PRs, files, or directories using BMad workflows.
bmod-core-tools
Core metadata module for BMad—set up via the bmad skill, not directly invoked.