# Soloscrum Tracker Linear Create Subtask

> Operation: create a Linear subtask under the Linear Task synced from a GitHub Issue. Used when active tracker profile is linear+github.

- Skill: `mew-ton/soloscrum-tracker-linear-create-subtask` (Agent Skill)
- Install (CLI): `npx get-skill add mew-ton/soloscrum-tracker-linear-create-subtask`
- Raw SKILL.md: https://api.skillmd.com/api/skills/mew-ton/soloscrum-tracker-linear-create-subtask/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Productivity
- Author: mew-ton (https://skillmd.com/u/mew-ton)
- Updated: 2026-11-18
- Page: https://skillmd.com/skills/mew-ton/soloscrum-tracker-linear-create-subtask

---


# soloscrum-tracker-linear-create-subtask

Creates a Linear subtask under the Linear Task that was auto-synced from a parent GH Issue. Active when `tracker_profile = linear+github`.

## Inputs

- `parent_issue_number` — parent GH Issue number (used to look up the synced Linear Task)
- `title` — subtask title
- `body` — subtask body in the lightweight work-body format per `soloscrum-define-issue-format`'s Subtask Body section (Parent / What / Checklist / Notes — Subtasks do **not** carry AC; the parent Issue owns the AC and the Subtask slices its delivery)
- `type` — `develop` or `design-ui` (per `soloscrum-define-task-type`)
- `sp` — story points (per `soloscrum-define-story-points`)

## Steps

1. Resolve the parent Linear Task ID from the synced GH Issue:
   - Linear MCP — `list_issues` with filter on `attachments.url` matching the GH Issue URL
2. Create the subtask:
   - Linear MCP — `save_issue` with:
     - `parentId` = parent Linear Task ID
     - `title` = `<title>`
     - `description` = `<body>`
     - `labelIds` = label for `type:<type>`
     - `estimate` = `<sp>`

## Output

- Linear subtask ID (e.g. `PRJ-42`)
- URL

## Notes

- The parent **GH Issue** is canonical — never create a Linear Task without a corresponding synced GH Issue
- If the GH→Linear sync hasn't completed yet, retry with backoff or prompt the user to wait
- SP is set inline at creation time via `estimate` — separate `set-sp` call only needed for later updates

