メニュー
Break down epics and features into concrete backlog tasks with dependencies. Use when planning work, decomposing large features, or organizing sprints. Trigger with "break down", "decompose", "plan feature", "create subtasks".
デフォルトでは、最初にソースを確認する Prompt が選択されています。直接コマンドに切り替えるか、ローカルコピーをダウンロードすることもできます。
インストールを決める前に、SKILL.md と SkillsMP に表示されている付属ファイルをお読みください。
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
直接コマンドでは確認用 Prompt が省略されます。実行前にソースを確認してください。
npx skills add https://github.com/GGPrompts/my-plugins --skill breakdownコマンドは1行のまま表示されます。コピー前に横へスクロールして全体を確認してください。
ローカルで確認しますか？SkillsMP が現在取得できるファイルをダウンロードできます。
Review code changes with parallel detection agents and smart fixing
Branch merging and conflict resolution patterns. Use when merging feature branches, handling conflicts, or cleaning up worktrees. Trigger with "merge branch", "resolve conflicts", "cleanup worktree".
Controls Chrome browser: takes screenshots, clicks buttons, fills forms, downloads images, inspects pages, captures network requests, checks console errors, debugs API issues. Use when: 'screenshot', 'click', 'fill form', 'download image', 'check browser', 'look at screen', 'capture page', 'check for errors', 'debug network', 'API failing', 'console errors'. Provides MCP tool discovery for 70 tabz_* browser automation tools.
SOC 職業分類に基づく
SKILL.md を表示中
| name | breakdown |
| description | Break down epics and features into concrete backlog tasks with dependencies. Use when planning work, decomposing large features, or organizing sprints. Trigger with "break down", "decompose", "plan feature", "create subtasks". |
| model | sonnet |
| allowed-tools | Read, Grep, Glob, Bash, Task |
Patterns for breaking down large features into concrete, parallelizable tasks.
1. Infrastructure
└── Types, contexts, schemas, state management
2. Core Implementation
└── Main components, business logic
3. Integration
└── Connect pieces, wire up routes
4. Polish
└── Edge cases, error handling, UX improvements
5. Validation
└── Tests, documentation updates
Example: Dark Mode
1. Create New
└── Build new pattern alongside old
2. Migrate
└── Move components one at a time
3. Cleanup
└── Remove old pattern, dead code
4. Verify
└── Update tests, ensure no regressions
Example: Move to React Query
1. Investigate (if complex)
└── Reproduce, identify root cause
2. Fix
└── Implement the solution
3. Verify
└── Add regression test
Most bugs don't need decomposition - only create subtasks for complex bugs requiring investigation.
| Size | Lines Changed | Files | Time | Example |
|---|---|---|---|---|
| XS | <20 | 1 | Minutes | Fix typo, add import |
| S | 20-100 | 1-2 | <1hr | Add helper function |
| M | 100-300 | 2-5 | Hours | Add component |
| L | 300+ | 5+ | Day | Feature module |
| XL | 1000+ | 10+ | Days | Architecture change |
Target: S-M tasks. XS is too granular, L-XL should be broken down.
A: Create database schema
B: Implement API endpoint (blocked by A)
C: Add frontend form (blocked by B)
A: Create shared context
B: Use in Header (blocked by A)
C: Use in Footer (blocked by A)
D: Use in Sidebar (blocked by A)
B, C, D: Independent features
E: Integration testing (blocked by B, C, D)
B: Update styles.css for Header
C: Update styles.css for Footer (blocked by B)
Even though B and C are conceptually parallel, they touch the same file.
Common conflict points:
styles.css, theme.ts)routes.tsx, App.tsx)store.ts, context.tsx)types.ts, interfaces.ts)testUtils.ts, fixtures.ts)When detected: Add dependency between tasks to sequence them.
Group tasks into waves:
## Wave 1 (Ready Now)
Tasks with no blockers - start immediately
## Wave 2 (After Wave 1)
Tasks blocked by Wave 1 - becomes ready when Wave 1 completes
## Wave 3 (After Wave 2)
Final integration, polish tasks
Max 3-5 tasks per wave for manageability.
Before finalizing breakdown: