Stats
Actions
Tags
'%20stop-opacity%3D'0.16'%2F%3E%3Cstop%20offset%3D'1'%20stop-color%3D'rgb(200%2C90%2C60)'%20stop-opacity%3D'0.03'%2F%3E%3C%2FlinearGradient%3E%3C%2Fdefs%3E%3Crect%20width%3D'320'%20height%3D'200'%20fill%3D'url(%23g)'%2F%3E%3Ccircle%20cx%3D'250'%20cy%3D'56'%20r%3D'92'%20fill%3D'rgb(200%2C90%2C60)'%20fill-opacity%3D'0.06'%2F%3E%3Ccircle%20cx%3D'64'%20cy%3D'172'%20r%3D'58'%20fill%3D'rgb(200%2C90%2C60)'%20fill-opacity%3D'0.05'%2F%3E%3C%2Fsvg%3E)
From implan
Writes a structured sprint retrospective in markdown table format (Went Well, Problems, Learnings, Risks) to capture context for future sessions.
How this skill is triggered — by the user, by Claude, or both
Slash command
/implan:retro [optional: specific sprint to retro][optional: specific sprint to retro]The summary Claude sees in its skill listing — used to decide when to auto-load this skill
Write a retro for the sprint just completed. Scope to the most recent sprint only, not the entire session or project.
Write a retro for the sprint just completed. Scope to the most recent sprint only, not the entire session or project.
$ARGUMENTS
If the user named a specific sprint, retro that. If empty, retro the most recent completed work.
Output as a single markdown table. Use <br> for multiple bullets within a cell.
| Category | Details |
|---|---|
| **Went well** | • Approaches or plan sections that worked as-is and should be repeated |
| **Problems** | • Plan inaccuracies, wrong assumptions, things that required workarounds |
| **Learnings** | • Key decisions made during implementation, plan changes applied |
| **Risks** | • Unresolved issues, fragile areas, unvalidated assumptions that could affect later sprints |
Always include all four categories. If a category has nothing substantive, write "Nothing notable". Do not pad with filler. Keep each bullet to 1-3 sentences. Be specific and factual; avoid vague summaries. Focus on information that would help a future session pick up work with full context.
If the user specifies a different format (e.g. bullet list, YAML block, plain text), use that instead.
npx claudepluginhub dawid-dahl-umain/augmented-ai-development --plugin implanFacilitates structured sprint retrospectives with formats like Start/Stop/Continue, 4Ls, and Sailboat. Generates prioritized action items and a summary.
Facilitates and documents team retrospectives with structured formats (Start/Stop/Continue, 4Ls, Mad/Sad/Glad, Sailboat). Use at sprint, project, or milestone end to capture what went well, what to improve, and action items.
Facilitates structured sprint or project retrospectives by gathering data from status reports and velocity metrics, identifying what went well and what needs improvement, and generating actionable items with owners and due dates.