About retro
A Start-Stop-Continue retrospective skill for reviewing a project, period, or process. It organizes specific behavioral changes into three categories and assigns owners, timing, and a priority for follow-up.
Key features
- 01Start-Stop-Continue format
- 02Actionable items by category
- 03Owner and timing fields
- 04Top priority and check-in
Use cases
- 01Retrospecting on a project period
- 02Choosing practices to begin or end
- 03Tracking agreed team changes
Install
Copy the command and run it in a terminal.
npx skills add https:/After installing, type/retroin Claude Code to confirm it loaded.
Details
From the project READMEStart-Stop-Continue Retrospective
Run a focused retrospective identifying what to Start, Stop, and Continue.
Instructions
Analyze the subject (project, period, process) and generate specific, actionable items for each category. Focus on behaviors and practices, not people.
Output Format
Subject: What period or topic are we reflecting on? Timeframe: What period does this cover?
START
New practices or behaviors to begin
| What to Start | Why | Owner | When |
|---|---|---|---|
| [Specific action] | [Benefit expected] | [Who] | [Start date] |
| [Specific action] | [Benefit expected] | [Who] | [Start date] |
| [Specific action] | [Benefit expected] | [Who] | [Start date] |
STOP
Current practices to eliminate
| What to Stop | Why | Owner | When |
|---|---|---|---|
| [Specific thing to stop] | [Problem it causes] | [Who] | [End date] |
| [Specific thing to stop] | [Problem it causes] | [Who] | [End date] |
| [Specific thing to stop] | [Problem it causes] | [Who] | [End date] |
CONTINUE
Things that are working well
| What to Continue | Why It Works | How to Protect It |
|---|---|---|
| [Working practice] | [Value it provides] | [How to ensure it continues] |
| [Working practice] | [Value it provides] | [How to ensure it continues] |
| [Working practice] | [Value it provides] | [How to ensure it continues] |
Top Priority The single most impactful change from this retro:
[Action] — because [reason]
Check-in When will we review if these changes are working?
[Date or trigger]
Guidelines
- Be specific: "Start daily standups" not "communicate more"
- Be behavioral: Focus on actions, not attitudes
- Balance: Aim for 3-5 items per category
- Celebrate Continues: Don't skip this section—recognize what's working
- Assign owners: Unowned actions don't happen
- One priority: If everything is important, nothing is
$ARGUMENTS