# Soloscrum Split Into Tasks

> Breaks a GitHub Issue into subtasks with type (develop or design-ui) and story point estimates. Registers each subtask via the tracker operation skill matching the active profile.

- Skill: `mew-ton/soloscrum-split-into-tasks` (Agent Skill)
- Install (CLI): `npx get-skill add mew-ton/soloscrum-split-into-tasks`
- Raw SKILL.md: https://api.skillmd.com/api/skills/mew-ton/soloscrum-split-into-tasks/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: mew-ton (https://skillmd.com/u/mew-ton)
- Updated: 2026-11-18
- Page: https://skillmd.com/skills/mew-ton/soloscrum-split-into-tasks

---


# 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

1. Read target Issue Goal, Acceptance Criteria, and Out of Scope: $ARGUMENTS
2. **Verify `/soloscrum:breakdown` is the right command** (per `soloscrum-define-issue-size`):
   - If the Issue likely bundles multiple intents (SP > 5 or `/soloscrum:breakdown` would produce > 5 Subtasks — both read as mis-scope smells), route back to `/soloscrum:refine` for Issue split rather than proceed.
   - If the Issue's intent is coherent and a single PR would be reviewable, skip `/soloscrum:breakdown` and go directly to `/soloscrum:develop` (per `CLAUDE.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.
3. **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`.
4. Calculate SP for each subtask (see `soloscrum-define-story-points`)
5. If subtask count exceeds `max_subtasks` (5) in `soloscrum-define-issue-size`, treat as a mis-scope smell — the Issue likely bundles multiple intents. Return to `/soloscrum:refine` rather than proceed.
6. 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-subtask`
   - `linear+github` → `soloscrum-tracker-linear-create-subtask`
7. If any subtask depends on another, also invoke the active profile's `add-dependency` operation 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-type`
- `soloscrum-define-story-points`
- `soloscrum-define-issue-size` (when `/soloscrum:breakdown` is 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)

