retro▌
phuryn/pm-skills · updated May 13, 2026
MDX-style export adds YAML metadata + attribution linking explainx.ai and this canonical listing URL.
Run a structured retrospective that surfaces insights and produces actionable improvements.
Sprint Retrospective Facilitator
Run a structured retrospective that surfaces insights and produces actionable improvements.
Context
You are facilitating a retrospective for $ARGUMENTS.
If the user provides files (sprint data, velocity charts, team feedback, or previous retro notes), read them first.
Instructions
-
Choose a retro format based on context (or let the user pick):
Format A — Start / Stop / Continue:
- Start: What should we begin doing?
- Stop: What should we stop doing?
- Continue: What's working well that we should keep?
Format B — 4Ls (Liked / Learned / Lacked / Longed For):
- Liked: What did the team enjoy?
- Learned: What new knowledge was gained?
- Lacked: What was missing?
- Longed For: What do we wish we had?
Format C — Sailboat:
- Wind (propels us): What's driving us forward?
- Anchor (holds us back): What's slowing us down?
- Rocks (risks): What dangers lie ahead?
- Island (goal): Where are we trying to get to?
-
If the user provides raw feedback (e.g., sticky notes, survey responses, Slack messages):
- Group similar items into themes
- Identify the most frequently mentioned topics
- Note sentiment patterns (frustration, energy, confusion)
-
Analyze the sprint performance:
- Sprint goal: achieved or not?
- Velocity vs. commitment (over-committed? under-committed?)
- Blockers encountered and how they were resolved
- Collaboration patterns (what worked, what didn't)
-
Generate prioritized action items:
Priority Action Item Owner Deadline Success Metric 1 [Specific, actionable improvement] [Name/Role] [Date] [How we'll know it worked] - Limit to 2-3 action items (more won't get done)
- Each must be specific, assignable, and measurable
- Reference previous retro actions if available — were they completed?
-
Create the retro summary:
## Sprint [X] Retrospective — [Date] ### Sprint Performance - Goal: [Achieved / Partially / Missed] - Committed: [X pts] | Completed: [Y pts] ### Key Themes 1. [Theme] — [summary] ### Action Items 1. [Action] — [Owner] — [By date] ### Carry-over from Last Retro - [Previous action] — [Status: Done / In Progress / Not Started]
Save as markdown. Keep the tone constructive — the goal is improvement, not blame.
How to use retro on Cursor
AI-first code editor with Composer
Prerequisites
Before installing skills in Cursor, ensure your development environment meets these requirements:
- ›Cursor installed and configured on your development machine
- ›Node.js version 16.0+ with npm package manager (verify with
node --version) - ›Active project directory or workspace where you want to add retro
Execute installation command
Execute the skills CLI command in your project's root directory to begin installation:
The skills CLI fetches retro from GitHub repository phuryn/pm-skills and configures it for Cursor.
Select Cursor when prompted
The CLI will show a list of available agents. Use arrow keys to navigate and space to select Cursor:
Verify installation
Confirm successful installation by checking the skill directory location:
Reload or restart Cursor to activate retro. Access the skill through slash commands (e.g., /retro) or your agent's skill management interface.
Security & Verification Notice
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 development environment. Always verify the publisher's identity, review recent commits, and test in isolated environments before production deployment.
List & Monetize Your Skill
Submit your Claude Code skill and start earning
Use Cases▌
User Story & Requirements Generation
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
Competitive Analysis
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
Roadmap Prioritization
Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs
Example
Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale
Make data-driven prioritization decisions faster
Stakeholder Communication
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
Implementation Guide▌
Prerequisites
- ›Claude Desktop or compatible AI client
- ›Access to product documentation and roadmap tools (Jira, Notion, etc.)
- ›Understanding of product management frameworks (RICE, Jobs-to-be-Done, etc.)
- ›Stakeholder contact information and communication channels
Time Estimate
30-60 minutes to see productivity improvements
Installation Steps
- 1.Install product management skill
- 2.Start with user story generation for known feature
- 3.Progress to competitive analysis: research 2-3 competitors
- 4.Use for roadmap prioritization: apply RICE/ICE scoring
- 5.Draft stakeholder communications and refine based on feedback
- 6.Build template library for recurring PM tasks
- 7.Share effective prompts with product team
Common Pitfalls
- ⚠Not validating competitive research—verify facts before sharing
- ⚠Accepting user stories without involving engineering team
- ⚠Over-relying on frameworks without qualitative judgment
- ⚠Not customizing outputs to company culture and communication style
- ⚠Skipping stakeholder validation of generated requirements
Best Practices▌
✓ Do
- +Validate research and competitive analysis with real data
- +Collaborate with engineering when generating technical requirements
- +Customize frameworks and templates to your company context
- +Use skill for first drafts, refine with stakeholder input
- +Document successful prompt patterns for PM tasks
- +Combine AI efficiency with human judgment and intuition
✗ Don't
- −Don't publish competitive analysis without fact-checking
- −Don't finalize user stories without engineering review
- −Don't make prioritization decisions solely on AI scoring
- −Don't skip customer validation of generated requirements
- −Don't ignore company-specific context and culture
💡 Pro Tips
- ★Provide context: company goals, constraints, customer feedback
- ★Ask for alternatives: 'Show 3 ways to prioritize this roadmap'
- ★Request stakeholder-specific formatting: 'Executive summary vs. engineering spec'
- ★Use skill for 70% generation + 30% customization to company needs
When to Use This▌
✓ 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.
Learning Path▌
- 1Basic: user stories, feature specs, status updates
- 2Intermediate: competitive analysis, prioritization frameworks, PRDs
- 3Advanced: product strategy, go-to-market planning, OKR setting
- 4Expert: product vision, market positioning, business model innovation
Discussion
Product Hunt–style comments (not star reviews)- No comments yet — start the thread.
Ratings
4.5★★★★★52 reviews- ★★★★★Diya Shah· Dec 28, 2024
Solid pick for teams standardizing on skills: retro is focused, and the summary matches what you get after install.
- ★★★★★Li Diallo· Dec 24, 2024
Keeps context tight: retro is the kind of skill you can hand to a new teammate without a long onboarding doc.
- ★★★★★Michael Sanchez· Dec 20, 2024
Registry listing for retro matched our evaluation — installs cleanly and behaves as described in the markdown.
- ★★★★★Daniel Farah· Nov 19, 2024
retro has been reliable in day-to-day use. Documentation quality is above average for community skills.
- ★★★★★Meera Jain· Nov 19, 2024
retro fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
- ★★★★★Maya Bhatia· Nov 15, 2024
I recommend retro for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
- ★★★★★Li Shah· Nov 11, 2024
retro reduced setup friction for our internal harness; good balance of opinion and flexibility.
- ★★★★★Li Sharma· Oct 10, 2024
Useful defaults in retro — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
- ★★★★★Maya Gonzalez· Oct 10, 2024
retro is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
- ★★★★★Chen Huang· Oct 6, 2024
retro reduced setup friction for our internal harness; good balance of opinion and flexibility.
showing 1-10 of 52