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.
Breaks down plans into Linear sub-issues with E2E test criteria. Triggers on "decompose", "break down plan", or after completing trackable plans. Creates testable, demo-able increments completable in one session.
/plugin marketplace add SaharCarmel/Sahar-claude-code-marketplace/plugin install sdlc@sahar-claude-code-marketplaceThis skill inherits all available tools. When active, it can use any tool Claude has access to.
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?" </example>
<example> user: "attach to MIX-123" assistant: "Creating sub-issues under MIX-123: 1. MIX-124: [Title] ✓ 2. MIX-125: [Title] ✓Done. Updated sdlc.md." </example>
This skill should be used when the user asks to "create a slash command", "add a command", "write a custom command", "define command arguments", "use command frontmatter", "organize commands", "create command with file references", "interactive command", "use AskUserQuestion in command", or needs guidance on slash command structure, YAML frontmatter fields, dynamic arguments, bash execution in commands, user interaction patterns, or command development best practices for Claude Code.
This skill should be used when the user asks to "create an agent", "add an agent", "write a subagent", "agent frontmatter", "when to use description", "agent examples", "agent tools", "agent colors", "autonomous agent", or needs guidance on agent structure, system prompts, triggering conditions, or agent development best practices for Claude Code plugins.
This skill should be used when the user asks to "create a hook", "add a PreToolUse/PostToolUse/Stop hook", "validate tool use", "implement prompt-based hooks", "use ${CLAUDE_PLUGIN_ROOT}", "set up event-driven automation", "block dangerous commands", or mentions hook events (PreToolUse, PostToolUse, Stop, SubagentStop, SessionStart, SessionEnd, UserPromptSubmit, PreCompact, Notification). Provides comprehensive guidance for creating and implementing Claude Code plugin hooks with focus on advanced prompt-based hooks API.