Stats
Actions
Tags
Help us improve
Share bugs, ideas, or general feedback.
From implan
Writes a structured sprint retrospective in markdown table format (Went Well, Problems, Learnings, Risks) to capture context for future sessions.
npx claudepluginhub dawid-dahl-umain/augmented-ai-development --plugin implanHow 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.
Facilitates structured sprint retrospectives with Start/Stop/Continue, 4Ls, or Sailboat formats. Analyzes team feedback and performance to generate prioritized action items with owners and deadlines.
Facilitates structured sprint retrospectives: collects feedback, analyzes sprint performance, and generates prioritized action items with owners and deadlines.
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.
Share bugs, ideas, or general feedback.
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.