agile-retrospective
When facilitating sprint retrospectives or team improvement sessions.
Best use case
agile-retrospective is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
When facilitating sprint retrospectives or team improvement sessions.
Teams using agile-retrospective should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/agile-retrospective/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How agile-retrospective Compares
| Feature / Agent | agile-retrospective | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
When facilitating sprint retrospectives or team improvement sessions.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
## When to Use When facilitating sprint retrospectives or team improvement sessions. ## Patterns ### Start/Stop/Continue Format ```markdown ## Sprint X Retrospective ### 🟢 START (new practices) - [What should we begin doing?] - [New tools, processes, habits] ### 🔴 STOP (remove friction) - [What should we stop doing?] - [What's not working?] ### 🟡 CONTINUE (keep doing) - [What's working well?] - [What should we keep?] ### 📋 Action Items | Action | Owner | Due | |--------|-------|-----| | [specific action] | [name] | [date] | ``` ### 4Ls Format (Alternative) ``` LIKED: What went well? LEARNED: What did we learn? LACKED: What was missing? LONGED: What do we wish for? ``` ### Facilitation Tips ``` 1. Timebox: 45-60 min max 2. Equal voice: everyone speaks 3. No blame: focus on process, not people 4. Action items: max 3, specific, owned 5. Follow-up: review last retro's actions first ``` ### Action Item Quality ``` ❌ "Improve communication" ✅ "Daily 10min sync at 9am, owner: @lead, starts Monday" ❌ "Write more tests" ✅ "Add integration tests for auth module, owner: @dev, by Sprint end" ``` ## Anti-Patterns - No action items (talk shop only) - Too many action items (>3 = none done) - Blame individuals instead of process - Skip reviewing last sprint's actions - Manager dominates discussion ## Verification Checklist - [ ] All team members contributed - [ ] Max 3 action items - [ ] Each action has owner + date - [ ] Previous actions reviewed - [ ] Notes documented
Related Skills
agile-product-owner
Agile product ownership toolkit for Senior Product Owner including INVEST-compliant user story generation, sprint planning, backlog management, and velocity tracking. Use for story writing, sprint planning, stakeholder communication, and agile ceremonies.
agile-planning
Generate agile release plans with sprints and roadmaps using unique sprint codes. Use when creating sprint schedules, product roadmaps, release planning, or when user mentions agile planning, sprints, roadmap, or release plans.
agile-metrics
Master agile metrics with velocity, burn-down charts, cycle time, and team health indicators for data-driven improvement.
agile-ceremonies
Agile ceremonies and sprint management specialist. Use when running standups, retrospectives, sprint planning, or tracking sprint progress.
session-retrospective
Review the current session to extract learnings and propose improvements to CLAUDE.md files and skills. Run at the end of a session or when asked to reflect on what was learned. Routes project-specific learnings to the project CLAUDE.md, universal patterns to the global ~/.claude/CLAUDE.md, and repeated workflows to skill creation/modification proposals. Triggers include "retrospective", "session retro", "振り返って", "何を学んだ？", "セッションの学び", "what did we learn?", "improve from this session".
agile-workflow
Orchestrate agile development workflows by invoking commands in sequence with checkpoint-based flow control. This skill should be used when the user asks to 'run the workflow', 'continue working', 'what's next', 'complete the task cycle', 'start my day', 'end the sprint', 'implement the next task', or wants guided step-by-step development assistance. Keywords: workflow, orchestrate, agile, task cycle, sprint, daily, implement, review, PR, standup, retrospective.
Agile Scrum
Comprehensive guide to Agile Scrum methodology including roles, ceremonies, artifacts, sprint planning, and best practices for iterative software development
agile-methodology
Apply agile development practices. Use when planning sprints, running ceremonies, or improving team processes. Covers Scrum, Kanban, and agile principles.
agile-coordinator
Orchestrate multiple worker agents to implement groomed tasks. Use when multiple ready tasks need implementation, when you want autonomous multi-task execution, or when coordinating batch development work. Keywords: coordinator, orchestrator, multi-task, parallel, workers, batch, autonomous.
Incident Retrospective
A postmortem (also called incident review or retrospective) is a structured process for analyzing incidents to understand what happened, why it happened, and how to prevent similar incidents in future
agent-ops-retrospective
Scan the current chat session for durable learnings (clarifications, corrections, decisions, pitfalls) and update .agent/memory.md. Use after critical review and before concluding work.
bgo
Automates the complete Blender build-go workflow, from building and packaging your extension/add-on to removing old versions, installing, enabling, and launching Blender for quick testing and iteration.