Structured sprint retrospective facilitation with three proven formats and actionable outcome tracking.
Works with
Offers three retrospective formats: Start-Stop-Continue, Mad-Sad-Glad, and 4Ls (Liked-Learned-Lacked-Longed For), each suited to different team dynamics and reflection styles
Enforces blame-free discussion, specific action items with owners and due dates, and limits to 2-3 actions per retrospective to ensure follow-through
Includes time-boxing guidance (1 hour), facilitator rotatio
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versionsprint-retrospectiveExecute the skills CLI command in your project's root directory to begin installation:
Fetches sprint-retrospective from supercent-io/skills-template and configures it for Cursor.
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
Confirm successful installation by checking the skill directory location:
Restart Cursor to activate sprint-retrospective. Access via /sprint-retrospective in your agent's command palette.
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your environment. Always review source, verify the publisher, and test in isolation before production.
Submit your Claude Code skill and start earning
Create detailed user stories, acceptance criteria, and feature specs
Example
Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios
Reduce spec writing time by 50%, ensure comprehensive coverage
Research competitors, compare features, identify gaps
Example
Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities
Complete competitive research in 2 hours instead of 2 days
Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs
Example
Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale
0
total installs
0
this week
88
GitHub stars
0
upvotes
Run in your terminal
0
installs
0
this week
88
stars
## Retrospective Template: Start-Stop-Continue
### START (Start doing)
- Make daily standups shorter (within 5 minutes)
- Use a code review checklist
- Introduce pair programming
### STOP (Stop doing)
- Deploying on Friday afternoons (rollback risk)
- Overusing emergency meetings
- Adding features without documentation
### CONTINUE (Keep doing)
- Weekly tech sharing session
- Automated tests
- Transparent communication
### Action Items
1. [ ] Change standup time from 9:00 → 9:30 (Team Lead)
2. [ ] Write a code review checklist document (Developer A)
3. [ ] Announce the "no Friday deployments" rule (Team Lead)
## Retrospective: Mad-Sad-Glad
### MAD (What made us mad)
- Urgent bugs after deployment (twice)
- Requirements changed frequently
- Unstable test environment
### SAD (What we wished went better)
- Not enough time for code reviews
- Documentation lagged behind
- Accumulating tech debt
### GLAD (What made us glad)
- New team members onboarded quickly
- CI/CD pipeline stabilized
- Positive customer feedback
### Action Items
- Strengthen the deployment checklist
- Improve the requirements change process
- Reserve documentation time every Friday
## Retrospective: 4Ls
### LIKED (What we liked)
- Great teamwork
- Successfully adopted a new tech stack
### LEARNED (What we learned)
- Standardize the local environment with Docker Compose
- Improve server state management with React Query
### LACKED (What we lacked)
- Performance testing
- Mobile support
### LONGED FOR (What we longed for)
- Better developer tools
- External training opportunities
### Action Items
- Automatically measure performance by introducing Lighthouse CI
- Write responsive design guidelines
# Sprint [N] Retrospective
**Date**: 2025-01-15
**Participants**: Team Member A, B, C, D
**Format**: Start-Stop-Continue
## What Went Well
- Completed all stories (Velocity: 25 points)
- 0 bugs
- Great team morale
## What Didn't Go Well
- Tech spike took longer than expected
- Rework due to design changes
## Action Items
1. [ ] Assign tech spikes to a dedicated sprint (Team Lead, ~01/20)
2. [ ] Introduce a pre-review process for designs (Designer, ~01/18)
3. [ ] Share the velocity chart (Scrum Master, weekly)
## Key Metrics
- Velocity: 25 points
- Bugs Found: 0
- Sprint Goal Achievement: 100%
#retrospective #agile #scrum #team-improvement #project-management
Make data-driven prioritization decisions faster
Draft PRDs, status updates, and stakeholder presentations
Example
Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement
Save 3-5 hours/week on communication overhead
Prerequisites
Time Estimate
30-60 minutes to see productivity improvements
Steps
Common Pitfalls
✓ Do
✗ Don't
💡 Pro Tips
✓ Use when
Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.
✗ Avoid when
Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.
supercent-io/skills-template
mattpocock/skills
parcadei/continuous-claude-v3
cursor/plugins
ailabs-393/ai-labs-claude-skills
pproenca/dot-skills
I recommend sprint-retrospective for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
sprint-retrospective reduced setup friction for our internal harness; good balance of opinion and flexibility.
sprint-retrospective has been reliable in day-to-day use. Documentation quality is above average for community skills.
Useful defaults in sprint-retrospective — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
Registry listing for sprint-retrospective matched our evaluation — installs cleanly and behaves as described in the markdown.
sprint-retrospective reduced setup friction for our internal harness; good balance of opinion and flexibility.
I recommend sprint-retrospective for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
sprint-retrospective fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
We added sprint-retrospective from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
sprint-retrospective reduced setup friction for our internal harness; good balance of opinion and flexibility.
showing 1-10 of 49