elixir/docs/logging.md requires these fields for issue/session lifecycle logs. Use
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 odysseus0/symphony --skill debugCompatible with
Supported agents
them as your join keys during debugging.
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versiondebugExecute the skills CLI command in your project's root directory to begin installation:
epx add odysseus0/symphony --skill debugFetches debug from odysseus0/symphony 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/debug
Restart Cursor to activate debug. Access via /debugin 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.
deslop
cursor/plugins · Productivity · same category
nutritional-specialist
ailabs-393/ai-labs-claude-skills · Productivity · same category
write-a-prd
mattpocock/skills · Productivity · same category
travel-planner
ailabs-393/ai-labs-claude-skills · Productivity · same category
wordpress-elementor
jezweb/claude-skills · Productivity · same category
reverse-engineering-tools
gmh5225/awesome-game-security · Productivity · same category
debug is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
Keeps context tight: debug is the kind of skill you can hand to a new teammate without a long onboarding doc.
debug has been reliable in day-to-day use. Documentation quality is above average for community skills.
debug reduced setup friction for our internal harness; good balance of opinion and flexibility.
debug fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
debug has been reliable in day-to-day use. Documentation quality is above average for community skills.
Registry listing for debug matched our evaluation — installs cleanly and behaves as described in the markdown.
Keeps context tight: debug is the kind of skill you can hand to a new teammate without a long onboarding doc.
I recommend debug for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
debug fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
showing 1-10 of 25