Dispatch fresh subagents per task with two-stage review (spec compliance, then code quality) in the current session.
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
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
Submit your Claude Code skill and start earning
epx add obra/superpowers --skill subagent-driven-developmentCompatible with
Supported agents
Isolates each task to a dedicated subagent with precisely crafted context, preventing context pollution and keeping the controller focused on coordination
Enforces a two-stage review cycle: spec compliance reviewer confirms the implementation matches requirements, then code quality reviewer checks for issues
Handles implementer status signals (DONE, DONE_WITH_CONCERNS,
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versionsubagent-driven-developmentExecute the skills CLI command in your project's root directory to begin installation:
epx add obra/superpowers --skill subagent-driven-developmentFetches subagent-driven-development from obra/superpowers 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:
.cursor/skills/subagent-driven-development
Restart Cursor to activate subagent-driven-development. Access via /subagent-driven-developmentin your agent's command palette.
Learn more:View source on GitHubSkills CLI docsAbout CursorWhat are agent skills?
Time estimate: 30-60 minutes to see productivity improvements
Prerequisites
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.
pyqt6-ui-development-rules
oimiragieo/agent-studio · Frontend · tag: development
yt-dlp
lwmxiaobei/yt-dlp-skill · Productivity · same category
xauusd-trading
huynguyen03dev/xauusd-trading · Productivity · same category
reverse-engineering-tools
gmh5225/awesome-game-security · Productivity · same category
smart-ocr
claude-office-skills/skills · Productivity · same category
cmux-browser
manaflow-ai/cmux · Productivity · same category
subagent-driven-development reduced setup friction for our internal harness; good balance of opinion and flexibility.
Registry listing for subagent-driven-development matched our evaluation — installs cleanly and behaves as described in the markdown.
subagent-driven-development fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
Keeps context tight: subagent-driven-development is the kind of skill you can hand to a new teammate without a long onboarding doc.
subagent-driven-development has been reliable in day-to-day use. Documentation quality is above average for community skills.
We added subagent-driven-development from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
subagent-driven-development fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
I recommend subagent-driven-development for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
Registry listing for subagent-driven-development matched our evaluation — installs cleanly and behaves as described in the markdown.
Useful defaults in subagent-driven-development — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
showing 1-10 of 55