ilandahan/AID / skills/memory-system/references/phases/breakdown
memory-system-breakdown
VerifiedReference for the Breakdown phase: work breakdown generation (see /jira-breakdown command).
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 1.4 KB |
| cumulative.md | markdown | 450 B |
SKILL.md
View on GitHub---
name: memory-system-breakdown
description: "Reference for the Breakdown phase: work breakdown generation (see /jira-breakdown command)."
---
# 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.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| planning-and-task-breakdownaddyosmani/agent-skillsBreaks work into ordered tasks. Use when you have a spec or clear requirements and need to break work into implementable tasks. Use when a task feels too large to start, when you need to estimate scope, or when parallel work is possible. | Stars: 119k | Updated | Claude CodeCodex | Verified | Install |
| screenpipethedotmack/claude-memSearch screen and audio history recorded by Screenpipe and optionally save selected context into claude-mem. Use when the user asks to recall desktop activity, a meeting, or something seen in another app through Screenpipe. | Stars: 118k | Updated | Claude CodeCodex | Verified | Install |
| contact-widgetnexu-io/open-designSelf-contained floating chat widget with welcome screen, social links, meeting button, and message input. Single HTML file, zero dependencies. | Stars: 108k | Updated | Claude CodeCodex | Verified | Install |
| meeting-notesnexu-io/open-designMeeting notes page — title bar with attendees, agenda checklist, decisions block, action items table with owners + dates, and a "next meeting" footer. Use when the brief mentions "meeting notes", "minutes", "1:1 notes", "all-hands recap", or "会议纪要". | Stars: 108k | Updated | Claude CodeCodex | Verified | Install |