Generates hierarchical work breakdown from epics down to individual tasks with INVEST-compliant user stories, technical enablers, and test items
Provides GitHub issue templates for each work item type (epic, feature, story, enabler, task) with acceptance criteria, definitions of done, and dependency linking
Includes priority and value matrix (P0–P3), Fibonacci story
Fetches breakdown-plan from github/awesome-copilot and configures it for Cursor.
3
Select Cursor when prompted
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
◆ Which agents do you want to install to?
│
│ ── Universal (.agents/skills) ────────────────
│ · Cline · Codex · Goose · Windsurf
│ ●Cursor(selected)
│ · Cursor · Aider · Continue
4
Verify installation
Confirm successful installation by checking the skill directory location:
.cursor/skills/breakdown-plan
Restart Cursor to activate breakdown-plan. Access via /breakdown-plan in your agent's command palette.
⚠
Security 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 environment. Always review source, verify the publisher, and test in isolation before production.
Act as a senior Project Manager and DevOps specialist with expertise in Agile methodology and GitHub project management. Your task is to take the complete set of feature artifacts (PRD, UX design, technical breakdown, testing plan) and generate a comprehensive GitHub project plan with automated issue creation, dependency linking, priority assignment, and Kanban-style tracking.
GitHub Project Management Best Practices
Agile Work Item Hierarchy
Epic: Large business capability spanning multiple features (milestone level)
Feature: Deliverable user-facing functionality within an epic
Story: User-focused requirement that delivers value independently
Enabler: Technical infrastructure or architectural work supporting stories
Test: Quality assurance work for validating stories and enablers
Task: Implementation-level work breakdown for stories/enablers
Feature Summary: Brief description and business value
Success Criteria: Measurable outcomes and KPIs
Key Milestones: Breakdown of major deliverables without timelines
Risk Assessment: Potential blockers and mitigation strategies
2. Work Item Hierarchy
graph TD
A[Epic:{Epic Name}]--> B[Feature:{Feature Name}] B --> C[Story 1:{User Story}] B --> D[Story 2:{User Story}] B --> E[Enabler 1:{Technical Work}] B --> F[Enabler 2:{Infrastructure}] C --> G[Task: Frontend Implementation] C --> H[Task: API Integration] C --> I[Test: E2E Scenarios] D --> J[Task: Component Development] D --> K[Task: State Management] D --> L[Test: Unit Tests] E --> M[Task: Database Schema] E --> N[Task: Migration Scripts] F --> O[Task: CI/CD Pipeline] F --> P[Task: Monitoring Setup]
3. GitHub Issues Breakdown
Epic Issue Template
# Epic: {Epic Name}## Epic Description{Epic summary from PRD}
## Business Value-**Primary Goal**: {Main business objective}
-**Success Metrics**: {KPIs and measurable outcomes}
-**User Impact**: {How users will benefit}
## Epic Acceptance Criteria- [ ] {High-level requirement 1}
- [ ] {High-level requirement 2}
- [ ] {High-level requirement 3}
## Features in this Epic- [ ] #{feature-issue-number} - {Feature Name}
## Definition of Done- [ ] All feature stories completed
- [ ] End-to-end testing passed
- [ ] Performance benchmarks met
- [ ] Documentation updated
- [ ] User acceptance testing completed
## Labels`epic`, `{priority-level}`, `{value-tier}`## Milestone{Release version/date}
## Estimate{Epic-level t-shirt size: XS, S, M, L, XL, XXL}
Feature Issue Template
# Feature: {Feature Name}## Feature Description{Feature summary from PRD}
## User Stories in this Feature- [ ] #{story-issue-number} - {User Story Title}
- [ ] #{story-issue-number} - {User Story Title}
## Technical Enablers- [ ] #{enabler-issue-number} - {Enabler Title}
- [ ] #{enabler-issue-number} - {Enabler Title}
## Dependencies**Blocks**: {List of issues this feature blocks}
**Blocked by**: {List of issues blocking this feature}
## Acceptance Criteria- [ ] {Feature-level requirement 1}
- [ ] {Feature-level requirement 2}
## Definition of Done- [ ] All user stories delivered
- [ ] Technical enablers completed
- [ ] Integration testing passed
- [ ] UX review approved
- [ ] Performance testing completed
## Labels`feature`, `{priority-level}`, `{value-tier}`, `{component-name}`## Epic#{epic-issue-number}## Estimate{Story points or t-shirt size}
User Story Issue Template
# User Story: {Story Title}## Story StatementAs a **{user type}**, I want **{goal}** so that **{benefit}**.
## Acceptance Criteria- [ ] {Specific testable requirement 1}
- [ ] {Specific testable requirement 2}
- [ ] {Specific testable requirement 3}
## Technical Tasks- [ ] #{task-issue-number} - {Implementation task}
- [ ] #{task-issue-number} - {Integration task}
## Testing Requirements- [ ] #{test-issue-number} - {Test implementation}
## Dependencies**Blocked by**: {Dependencies that must be completed first}
## Definition of Done- [ ] Acceptance criteria met
- [ ] Code review approved
- [ ] Unit tests written and passing
- [ ] Integration tests passing
- [ ] UX design implemented
- [ ] Accessibility requirements met
## Labels`user-story`, `{priority-level}`, `frontend/backend/fullstack`, `{component-name}`## Feature#{feature-issue-number}## Estimate{Story points: 1, 2, 3, 5, 8}
›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
Steps
1Install product management skill
2Start with user story generation for known feature
3Progress to competitive analysis: research 2-3 competitors
4Use for roadmap prioritization: apply RICE/ICE scoring
5Draft stakeholder communications and refine based on feedback
6Build template library for recurring PM tasks
7Share 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
