메뉴
Break down epics into implementable user stories with acceptance criteria, estimates, dependencies, and sprint groupings. This skill should be used for epic planning and backlog grooming.
기본적으로 소스를 먼저 확인하는 Prompt가 선택됩니다. 직접 명령으로 전환하거나 로컬 사본을 다운로드할 수도 있습니다.
설치 여부를 결정하기 전에 SKILL.md와 SkillsMP에 표시된 보조 파일을 읽어 보세요.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
직접 명령은 검토 Prompt를 거치지 않습니다. 실행하기 전에 소스를 확인하세요.
npx skills add https://github.com/adolfoaranaes12/BMAD-ENHANCED --skill breakdown-epic명령은 한 줄로 유지됩니다. 복사하기 전에 가로로 스크롤해 전체 내용을 확인하세요.
로컬 사본을 원하시나요? SkillsMP에서 현재 제공할 수 있는 파일을 다운로드하세요.
SKILL.md 표시 중
| name | breakdown-epic |
| description | Break down epics into implementable user stories with acceptance criteria, estimates, dependencies, and sprint groupings. This skill should be used for epic planning and backlog grooming. |
| acceptance | [{"components_identified":"Major components and sub-features identified from epic"},{"stories_created":"User stories created in proper format with acceptance criteria"},{"estimates_provided":"Story points estimated using complexity/effort/risk"},{"dependencies_mapped":"Dependencies between stories identified and documented"},{"sprints_suggested":"Sprint groupings suggested based on dependencies and priorities"}] |
| inputs | {"epic_description":{"type":"string","required":true,"description":"Epic or feature description to break down"},"tech_stack":{"type":"array","required":false,"description":"Technology stack for technical considerations"}} |
| outputs | {"story_files":{"type":"array","description":"List of generated story file paths"},"epic_file":{"type":"string","description":"Path to generated epic summary file"},"total_points":{"type":"number","description":"Total story points across all stories"},"story_count":{"type":"number","description":"Number of stories created"},"sprint_count":{"type":"number","description":"Suggested number of sprints"}} |
| telemetry | {"emit":"skill.breakdown-epic.completed","track":["story_count","total_points","sprint_count","priority_distribution","dependency_count","duration_ms"]} |
Transform high-level epics or features into detailed, actionable user stories ready for sprint planning and implementation.
Core Capabilities:
.claude/config.yaml) with planning settingsAction: Load configuration and parse epic requirements.
Load config: Read .claude/config.yaml for planning settings (storiesLocation, epicsLocation, defaultVelocity, storyPointScale, techStack)
Get epic description: From user input (20+ words minimum), parse scope, business goals, technical requirements
Prepare directories: Create stories and epics directories
See: references/templates.md#configuration-format and #step-0-configuration-loading for details
Halt if:
See: references/epic-analysis-guide.md for scope analysis
Action: Break down epic into major components and sub-features.
Identify components:
Output: Epic analysis with major components, sub-features, user types, technical/security requirements, NFRs
See: for complete analysis format
references/templates.md#step-1-epic-analysis-exampleGroup by themes:
See: references/epic-analysis-guide.md for detailed analysis techniques
Action: Convert components into user stories with acceptance criteria.
Story format: "As a [user], I want [capability], So that [benefit]" with acceptance criteria, priority, component
See: references/templates.md#step-2-user-story-format for format and 5 complete examples
Story quality checks:
See: references/story-creation-guide.md for story writing best practices
Action: Estimate each story using complexity, effort, and risk.
Estimation factors: Complexity (1-5), Effort (1-5), Risk (1-3)
Calculate: Story Points = Complexity + Effort + Risk, round to Fibonacci (1, 2, 3, 5, 8, 13, 21)
See: references/templates.md#step-3-estimation-factors-template for detailed scales and examples
See: references/estimation-guide.md for detailed estimation techniques
Action: Map dependencies between stories.
Dependency types:
1. Blocks: Story A must complete before Story B can start
story-auth-001 (Signup) BLOCKS story-auth-003 (Email Verification)
2. Related: Stories share components but can be done in parallel
story-auth-001 (Signup) RELATED story-auth-002 (Login)
Dependency rules:
Output: Dependency graph with BLOCKS/REQUIRES/RELATED relationships, critical path identification
See: references/templates.md#step-4-dependency-examples for complete graph format
See: references/dependency-mapping-guide.md for dependency analysis
Action: Group stories into sprints based on dependencies, priorities, and velocity.
Grouping rules:
Output: Sprint groupings with story assignments, velocity constraints, dependency respect, logical grouping
See: references/templates.md#step-5-sprint-grouping-example for complete sprint plan format
Action: Create story markdown files and epic summary.
Generate files: Use bmad-commands write_file for each story and epic summary
Output: Story files (complete format with user story, ACs, dependencies, estimation, DoD) and epic summary file
See: references/templates.md#step-6-story-file-format-template and #step-6-epic-summary-file-format for complete structures
Action: Present epic breakdown summary for review.
Output: Breakdown complete summary with story count, points, sprints, files, priorities, sprint plan, dependencies
See: references/templates.md#step-7-summary-output-template for complete format
Return structured JSON with story_files, epic_file, metrics (total_points, story_count, sprint_count), and telemetry
See: references/templates.md#json-output-format for complete structure
See: references/story-creation-guide.md for best practices
Use this skill when:
Always use before:
Feeds into:
Detailed documentation in references/:
Part of BMAD Enhanced Planning Suite
Comprehensive brownfield architecture analysis for existing codebases. Discovers structure, identifies patterns, assesses quality, calculates production readiness, and provides actionable recommendations. Use when analyzing existing codebases to understand architecture, assess quality, or prepare for modernization.
Systematically consume QA quality gate outputs and apply prioritized fixes for high-severity issues, NFR failures, and test coverage gaps. Use when quality review identifies issues requiring remediation.
Peer review architecture for quality, risks, and optimization opportunities. Analyzes scalability bottlenecks, security vulnerabilities, performance optimization, technology fit, and provides prioritized recommendations. Use when reviewing proposed architecture documents for quality assurance, risk identification, or architectural decision validation.
SOC 직업 분류 기준
