Retrospectives are critical ceremonies for team learning and continuous improvement. Effective facilitation creates psychological safety, encourages honest feedback, and drives tangible improvements.
Works with
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versionretrospective-facilitationExecute the skills CLI command in your project's root directory to begin installation:
Fetches retrospective-facilitation from aj-geddes/useful-ai-prompts 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 retrospective-facilitation. Access via /retrospective-facilitation 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
161
GitHub stars
0
upvotes
Run in your terminal
0
installs
0
this week
161
stars
Retrospectives are critical ceremonies for team learning and continuous improvement. Effective facilitation creates psychological safety, encourages honest feedback, and drives tangible improvements.
Minimal working example:
Retrospective Planning:
Event: Sprint 23 Retrospective
Date: Friday, Jan 17, 2025
Duration: 60 minutes
Location: Conference Room B / Zoom
Facilitator: Sarah (Scrum Master)
Participants: 8 team members
Invite: Product Owner (optional)
---
Retrospective Goals: 1. Celebrate sprint successes
2. Identify what went well
3. Identify what could improve
4. Commit to specific improvements
5. Build team cohesion
Format: "Went Well / Didn't Go Well / Ideas"
Tool: Miro board for virtual collaboration
Pre-Retrospective Preparation:
- Send survey: anonymous feedback (24hrs before)
- Gather sprint metrics (velocity, bugs, etc.)
- Review sprint goals and outcomes
// ... (see reference guides for full implementation)
Detailed implementations in the references/ directory:
| Guide | Contents |
|---|---|
| Retrospective Planning | Retrospective Planning |
| Facilitation Techniques | Facilitation Techniques |
| Action Item Tracking | Action Item Tracking |
| Retrospective Templates | Retrospective Templates |
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.
mattpocock/skills
parcadei/continuous-claude-v3
cursor/plugins
ailabs-393/ai-labs-claude-skills
pproenca/dot-skills
mattpocock/skills
We added retrospective-facilitation from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
Useful defaults in retrospective-facilitation — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
retrospective-facilitation is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
I recommend retrospective-facilitation for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
retrospective-facilitation fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
Solid pick for teams standardizing on skills: retrospective-facilitation is focused, and the summary matches what you get after install.
retrospective-facilitation has been reliable in day-to-day use. Documentation quality is above average for community skills.
retrospective-facilitation reduced setup friction for our internal harness; good balance of opinion and flexibility.
Useful defaults in retrospective-facilitation — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
Keeps context tight: retrospective-facilitation is the kind of skill you can hand to a new teammate without a long onboarding doc.
showing 1-10 of 63