retro
Facilitate a team retrospective
SKILL.mdplugins/leadership/skills/retro/SKILL.md
GitHubRetrospective
Facilitate a retrospective for "$ARGUMENTS". Structure a team reflection on what went well, what didn't, and what to improve.
See also /project-management:retrospective for the sprint ceremony — format, dot-voting and committed action items tied to last sprint.
Arguments. $ARGUMENTS may contain the project name and optional flags. Take the first token as <project> and treat --skip-checks as a flag; never include flags in file paths. All paths below use <project>. If --skip-checks is present, skip the prerequisite check and, before writing any artifact, append one line to .metapowers/leadership/<project>/skip-log.md: - <ISO timestamp> — <skill name> skipped prerequisite check for <artifact file> — reason: <reason or "none given">.
Prerequisites
None — utility skill, run anytime.
Process
Set the context:
- What period or project is this retro for?
- Who participated? What was the scope?
Structure the retro (Start/Stop/Continue format):
- Start: What should we begin doing?
- Stop: What should we stop doing?
- Continue: What's working well and should continue?
Dig deeper:
- For each item: why? What's the root cause?
- What patterns repeat from previous retros?
- Are there systemic issues to address?
Define action items:
- Convert insights into 2-3 specific, assignable actions
- Each action has an owner and a deadline
- Focus on highest-impact changes
Write the artifact to
.metapowers/leadership/<project>/retro.mdwith sections:- Context — period, team, scope
- Start — new practices to adopt
- Stop — practices to drop
- Continue — practices to maintain
- Action Items — owner, action, deadline
Output
The retro summary written to .metapowers/leadership/<project>/retro.md. Present the key insights and action items to the user.