| name | decompose |
| description | Break down a Claude Code plan into Linear sub-issues with E2E test criteria. Use when: user says "decompose", "break down plan", "create issues from plan", or after completing a plan that needs to be tracked in Linear. Each sub-issue is self-contained (completable in one Claude Code session) and testable from the user's perspective. |
Flow
- Check
sdlc.mdfor team/project context (ask user if missing or ambiguous) - Analyze plan from conversation memory
- Break into testable increments
- Generate E2E tests for each increment
- Show preview and ask: "Create new parent or attach to existing?"
- Confirm target (team/project) before creating
- Create issues in Linear with
parentIdfor sub-issues - Update
sdlc.mdwith created issue IDs
Increment Rules
Each sub-issue MUST:
- Deliver one testable artifact (something demo-able)
- Be completable by Claude Code in one session
- Include E2E test criteria
Prefer smaller over larger. Order by dependency chain.
E2E Test Format
### Happy Path
- [ ] User can [action] and [expected result]
### Edge Cases
- [ ] [boundary condition scenario]
Sub-Issue Template
## Summary
[What this delivers]
## Deliverable
[The testable artifact]
## E2E Test Scenarios
### Happy Path
- [ ] User can [action] and [expected result]
### Edge Cases
- [ ] [Edge case]
## Implementation Notes
[Context from plan]
Examples
1. [Title]
- Deliverable: [artifact]
- E2E: User can [action] and [result]
2. [Title]
- Deliverable: [artifact]
- E2E: User can [action] and [result]
Target: Team 'Engineering', Project 'My Project'
Create new parent issue or attach to existing?"
Done. Updated sdlc.md."