YOU MUST EXECUTE THIS WORKFLOW. Do not just describe it.
Works with
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versionretroExecute the skills CLI command in your project's root directory to begin installation:
Fetches retro from boshu2/agentops 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 retro. Access via /retro 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
260
GitHub stars
0
upvotes
Run in your terminal
0
installs
0
this week
260
stars
YOU MUST EXECUTE THIS WORKFLOW. Do not just describe it.
Quick-capture a learning to the knowledge flywheel. For comprehensive retrospectives with backlog processing, activation, and retirement, use /post-mortem.
Given /retro --quick "insight text" or /retro "insight text":
.agents/learnings/YYYY-MM-DD-quick-<slug>.md:---
type: learning
source: retro-quick
date: YYYY-MM-DD
maturity: provisional
utility: 0.5
---
# Learning: <Short Title>
**Category**: <auto-classify: debugging|architecture|process|testing|security>
**Confidence**: medium
## What We Learned
<user's insight text>
## Source
Quick capture via `/retro --quick`
Learned: <one-line summary>
Saved to: .agents/learnings/YYYY-MM-DD-quick-<slug>.md
For comprehensive knowledge extraction, use `/post-mortem`.
Done. Return immediately after confirmation.
User says: /retro --quick "macOS cp alias prompts on overwrite — use /bin/cp to bypass"
What happens:
macos-cp-alias-overwrite.agents/learnings/2026-03-03-quick-macos-cp-alias-overwrite.mdLearned: macOS cp alias prompts — use /bin/cp| Problem | Cause | Solution |
|---|---|---|
| Learning too generic | Surface-level capture | Be specific: "auth tokens expire after 1h" not "learned about auth" |
| Duplicate learnings | Same insight captured twice | Check existing learnings with grep before writing |
| Need full retrospective | Quick capture isn't enough | Use /post-mortem for comprehensive extraction + processing |
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
pproenca/dot-skills
ailabs-393/ai-labs-claude-skills
mattpocock/skills
retro reduced setup friction for our internal harness; good balance of opinion and flexibility.
retro reduced setup friction for our internal harness; good balance of opinion and flexibility.
Registry listing for retro matched our evaluation — installs cleanly and behaves as described in the markdown.
Useful defaults in retro — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
Solid pick for teams standardizing on skills: retro is focused, and the summary matches what you get after install.
Solid pick for teams standardizing on skills: retro is focused, and the summary matches what you get after install.
I recommend retro for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
retro reduced setup friction for our internal harness; good balance of opinion and flexibility.
I recommend retro for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
I recommend retro for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
showing 1-10 of 50