> **Source**: `../../commands/jira-breakdown.md` > > This file is a reference. The main prompt is in the `../../commands/` directory. > Use the `/jira-breakdown` command for work breakdown generation.
Scanned 9/9/2026
Install to Claude Code
Skills Directorynpx -y skills add ilandahan/AID --skill breakdown --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Breakdown?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/ilandahan-breakdown)More formats (shields.io, HTML) on the badges page.
# Breakdown Phase Skill
> **Source**: `../../commands/jira-breakdown.md`
>
> This file is a reference. The main prompt is in the `../../commands/` directory.
> Use the `/jira-breakdown` command for work breakdown generation.
## Quick Reference
**Phase**: 3 - Breakdown
**Command**: `/jira-breakdown [feature-name]`
**Output**: Epics, Stories, Tasks, Subtasks with estimates
### Entry Criteria
- Tech Spec phase completed and approved
- Architecture decisions documented
- API contracts defined
- Data models specified
### Exit Criteria
- All work items created in breakdown
- Estimates assigned (Story Points + Hours)
- Dependencies documented
- Sprint plan created
- Team review completed
### Jira Hierarchy
| Level | Size | Contains |
|-------|------|----------|
| Epic | 2-6 weeks | 3-10 Stories |
| Story | 1-5 days | 2-5 Tasks |
| Task | 2-8 hours | 2-6 Subtasks |
| Subtask | 30min-2h | — |
### Key Deliverables
1. Epic Overview (with priorities)
2. Stories with User Story format + Acceptance Criteria
3. Tasks with technical descriptions + estimates
4. Subtasks as atomic work units
5. Dependencies Map
6. Sprint Plan
7. Risk Assessment
## Cumulative Learnings
See `cumulative.md` for project-specific learnings captured by the memory system.
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!
Ultra-compressed commit message generator. Cuts noise from commit messages while preserving intent and reasoning. Conventional Commits format. Subject ≤50 chars, body only when "why" isn't obvious. Use when user says "write a commit", "commit message", "generate commit", "/commit", or invokes /caveman-commit. Auto-triggers when staging changes.
Ultra-compressed code review comments. Cuts noise from PR feedback while preserving the actionable signal. Each comment is one line: location, problem, fix. Use when user says "review this PR", "code review", "review the diff", "/review", or invokes /caveman-review. Auto-triggers when reviewing pull requests.
一个全面的 Claude Code 会话验证系统。
Verification loop for Spring Boot projects: build, static analysis, tests with coverage, security scans, and diff review before release or PR.
Verification loop for Django projects: migrations, linting, tests with coverage, security scans, and deployment readiness checks before release or PR.
