Conduct Retrospective
Skill Verified ActiveConduct a project or sprint retrospective by gathering data from status reports and velocity metrics, structuring what went well and what needs improvement, and generating actionable improvement items with owners and due dates. Use at the end of a sprint, after a project phase or milestone, following a significant incident or success, at a quarterly review of ongoing processes, or before starting a similar project to capture lessons learned.
To provide a structured and evidence-based process for conducting project retrospectives, driving continuous improvement by identifying key learnings and generating actionable steps.
Features
- Gathers data from status reports and velocity metrics
- Structures findings into 'What Went Well' and 'What Needs Improvement'
- Generates actionable improvement items with owners and due dates
- Reviews previous action items for closure
- Produces a formal retrospective report
Use Cases
- At the end of a sprint for sprint retrospectives
- After a project phase or milestone completion
- Following significant incidents, failures, or successes
- During quarterly reviews of ongoing processes
- Before starting a similar project to capture lessons learned
Non-Goals
- Conducting daily stand-ups
- Managing the project backlog directly
- Creating project charters or work breakdown structures
- Replacing team-based discussion entirely; it structures and guides it
Workflow
- Gather Retrospective Data
- Structure What Went Well
- Structure What Needs Improvement
- Generate Improvement Actions
- Review Previous Actions and Write Report
Practices
- Continuous Improvement
- Agile Methodologies
- Project Management
- Lessons Learned
Prerequisites
- Project artifacts (status reports, sprint plans, backlog data)
- Access to file system for reading reports and writing the retrospective document
Practical Utility
- info:Usage examplesWhile the SKILL.md describes the output formats, concrete, ready-to-run end-to-end examples are not provided.
Installation
/plugin install agent-almanac@pjt222-agent-almanacQuality Score
VerifiedTrust Signals
Similar Extensions
Sprint Plan
100Plan a sprint with capacity estimation, story selection, dependency mapping, and risk identification. Use when preparing for sprint planning, estimating team capacity, selecting stories, or balancing sprint scope against velocity.
Scrum Master Expert
100Advanced Scrum Master skill for data-driven agile team analysis and coaching. Use when the user asks about sprint planning, velocity tracking, retrospectives, standup facilitation, backlog grooming, story points, burndown charts, blocker resolution, or agile team health. Runs Python scripts to analyse sprint JSON exports from Jira or similar tools: velocity_analyzer.py for Monte Carlo sprint forecasting, sprint_health_scorer.py for multi-dimension health scoring, and retrospective_analyzer.py for action-item and theme tracking. Produces confidence-interval forecasts, health grade reports, and improvement-velocity trends for high-performing Scrum teams.
Plan Sprint
99Plan a sprint by refining backlog items, defining a sprint goal, calculating team capacity, selecting items, and decomposing them into tasks. Produces a SPRINT-PLAN.md with goal, selected items, task breakdown, and capacity allocation. Use when starting a new sprint in a Scrum or agile project, re-planning after significant scope change, transitioning from ad-hoc work to structured sprint cadence, or after backlog grooming when items are ready for inclusion.
Github Project Management
99Comprehensive GitHub project management with swarm-coordinated issue tracking, project board automation, and sprint planning
Retro
99Facilitate a structured sprint retrospective — what went well, what didn't, and prioritized action items with owners and deadlines. Use when running a retrospective, reflecting on a sprint, creating action items from team feedback, or learning how to run effective retros.
Kaizen
99Use when Code implementation and refactoring, architecturing or designing systems, process and workflow improvements, error handling and validation. Provide tehniquest to avoid over-engineering and apply iterative improvements.