Retro

Retrospective

Facilitate a retrospective for "$ARGUMENTS". Structure a team reflection on what went well, what didn't, and what to improve.

Prerequisites

None — utility skill, run anytime.

Process

1. Set the context:

   • What period or project is this retro for?
   • Who participated? What was the scope?

2. 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?

3. Dig deeper:

   • For each item: why? What's the root cause?
   • What patterns repeat from previous retros?
   • Are there systemic issues to address?

4. Define action items:

   • Convert insights into 2-3 specific, assignable actions
   • Each action has an owner and a deadline
   • Focus on highest-impact changes

5. Write the artifact to .metapowers/leadership/$ARGUMENTS/retro.md with 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/$ARGUMENTS/retro.md. Present the key insights and action items to the user.