soloscrum-split-into-tasks
Decompose an Issue into subtasks with type and SP, then register them via the active profile's tracker operation.
Overview
Decomposes an Issue into implementable subtasks based on its AC and Goal. Assigns type (develop / design-ui) and SP to each subtask, then delegates registration to the tracker operation skill that matches the active profile (soloscrum-define-tracker-profile).
Steps
- Read target Issue Goal, Acceptance Criteria, and Out of Scope: $ARGUMENTS
- Verify
/soloscrum:breakdownis the right command (persoloscrum-define-issue-size):- If the Issue likely bundles multiple intents (SP > 5 or
/soloscrum:breakdownwould produce > 5 Subtasks — both read as mis-scope smells), route back to/soloscrum:refinefor Issue split rather than proceed. - If the Issue's intent is coherent and a single PR would be reviewable, skip
/soloscrum:breakdownand go directly to/soloscrum:develop(perCLAUDE.md's "Issues that fit within a single develop unit can skip this step"). - Only continue with the decomposition below when intent is coherent and a single PR would not be reviewable.
- If the Issue likely bundles multiple intents (SP > 5 or
- Decompose the Issue's delivery into reviewable work slices. Each Subtask is one slice of the parent intent that can be shipped in one reviewable PR (per
soloscrum-define-issue-format's Subtask Body section). Subtasks do not carry their own AC — they slice the parent's delivery, and their done condition is "lands an artefact the parent's AC verifiably depends on, or strictly advances the parent's AC checklist count, without regressions."- Slice along reviewability seams — file cluster, layer (backend / frontend), or phase (core / error handling / performance) when each slice produces a deliverable that can be reviewed on its own correctness/no-regression terms. Not along intent boundaries — that's an Issue split (see
soloscrum-define-issue-size), not a Subtask split. - 1 Subtask = 1 reviewable PR. Organise so dependencies between Subtasks are minimal and explicit.
- Assign type using
soloscrum-define-task-type.
- Slice along reviewability seams — file cluster, layer (backend / frontend), or phase (core / error handling / performance) when each slice produces a deliverable that can be reviewed on its own correctness/no-regression terms. Not along intent boundaries — that's an Issue split (see
- Calculate SP for each subtask (see
soloscrum-define-story-points) - If subtask count exceeds
max_subtasks(5) insoloscrum-define-issue-size, treat as a mis-scope smell — the Issue likely bundles multiple intents. Return to/soloscrum:refinerather than proceed. - After user approval, resolve the active profile via
soloscrum-define-tracker-profile, then for each subtask invoke the matching operation skill:github-only→soloscrum-tracker-github-create-subtasklinear+github→soloscrum-tracker-linear-create-subtask
- If any subtask depends on another, also invoke the active profile's
add-dependencyoperation skill
Output Format
## Subtask Breakdown Proposal
| # | Title | Type | SP |
|---|-------|------|----|
| 1 | [Title] | develop | 2 |
| 2 | [Title] | design-ui | 1 |
Total SP: 3
Depends On
soloscrum-define-issue-format(Subtask body contract: no AC, work slice of parent intent)soloscrum-define-task-typesoloscrum-define-story-pointssoloscrum-define-issue-size(when/soloscrum:breakdownis the right command, and the mis-scope-smell threshold)soloscrum-define-tracker-profile(routing)soloscrum-tracker-{github|linear}-create-subtask(delegated)soloscrum-tracker-{github|linear}-add-dependency(delegated, when needed)