From sdlc
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.
How this skill is triggered — by the user, by Claude, or both
Slash command
/sdlc:skills/decomposeThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
1. Check `sdlc.md` for team/project context (ask user if missing or ambiguous)
sdlc.md for team/project context (ask user if missing or ambiguous)parentId for sub-issuessdlc.md with created issue IDsEach sub-issue MUST:
Prefer smaller over larger. Order by dependency chain.
### Happy Path
- [ ] User can [action] and [expected result]
### Edge Cases
- [ ] [boundary condition scenario]
## 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]
1. [Title]
2. [Title]
Target: Team 'Engineering', Project 'My Project'
Create new parent issue or attach to existing?"
user: "attach to MIX-123" assistant: "Creating sub-issues under MIX-123: 1. MIX-124: [Title] ✓ 2. MIX-125: [Title] ✓Done. Updated sdlc.md."
npx claudepluginhub saharcarmel/sahar-claude-code-marketplace --plugin sdlcBreaks plans, specs, or PRDs into independently-grabbable issues on the project issue tracker using tracer-bullet vertical slices. Useful for turning high-level direction into actionable, demoable tasks.
Breaks down plans, specs, or PRDs into independent issues using vertical slices (tracer bullets). Useful for converting plans into implementation tickets or breaking down work into granular, demo-able tasks.
Breaks product requirement documents (PRDs) or plans into independently grabbable vertical slice issues, with dependency ordering and HITL/AFK labels.