| name | jira-structure |
| description | Generate a complete JIRA epic/story hierarchy with acceptance criteria, sprint planning, issue type taxonomy, labels, and team assignments. Use after project plan defines phases. |
| allowed-tools | Read, Grep, Glob, WebSearch |
Generate JIRA-STRUCTURE.md at the repository root.
Process
- Read
PROJECT-PLAN.md for phases, goals, and timeline
- Read
_research/DOMAIN-RESEARCH.md for terminology and team structure
- Decompose each phase into 2-5 epics (10-20 total)
- Decompose each epic into 3-8 stories (40-80 total)
- Define acceptance criteria for every story
- Plan sprint allocation across timeline
Required Sections
- Epic Hierarchy: Mermaid
mindmap showing all epics grouped by phase
- Epic Definitions (per phase):
- Epic ID, title, owner, duration, priority, dependencies
- Acceptance criteria (checkbox list)
- Stories with "As a... I want... So that..." format
- Story tasks (checkbox list) and acceptance criteria
- Issue Type Reference: Table (Type | When to Use | Example) covering Epic, Story, Task, Bug, Spike
- Labels & Components: Tables defining project labels and component ownership
- Sprint Planning: Cadence, total sprints, ceremony list
- Sprint Allocation: Table (Sprint | Dates | Phase | Epics | Story Points)
- Team Assignments: Table (Area | Owner Team | Epic IDs)
Scaling Rules
| Project Size | Epics | Stories | Sprints |
|---|
| Small (1-3mo) | 5-8 | 20-30 | 3-6 |
| Medium (3-6mo) | 10-15 | 40-60 | 6-12 |
| Large (6+mo) | 15-25 | 60-100 | 12+ |
Quality Criteria
