gh-tasklisted

# gh-task Add a task to an existing feature. ## When to use - A feature has multiple discrete steps that should be tracked - The user says "add a task to #N", "track sub-step X under #N" - During breakdown, when a step is too small to warrant its own issue ## Decision: sub-issue vs. checkbox | Effort | Mechanism | |---|---| | < 30 min, no separate verification needed | Checkbox in parent feature body | | ≥ 30 min OR has its own evidence | Real sub-issue with `type:chore` or `type:feature` (kind decided by user) | ## Inputs Required: - `parent` — feature issue number the task hangs off - `description` — what the task is Optional: - `severity` — `critical | high | medium | low`. Defaults to **the parent feature's severity** (read the parent's `severity:*` label, or its Project v2 `Severity` field if a project is attached). Override only when the task is meaningfully more or less urgent than its parent. Resolved against `workflows/default.yaml.severities.values[]`. - `kind` — `chore` or `feature`, defaults to `chore` for sub-issue path. ## What it does — sub-issue path 1. Resolve severity: use the explicit `severity` if provided, else read the parent's `severity:*` label (or Project v2 `Severity` field), else fall back to `workflows/default.yaml.severities.default`. 2. Same flow as `/gh-pms:gh-feature` with kind=chore (or kind specified) — pass the resolved severity through. 3. Calls `mcp__github__sub_issue_write` to link as sub-issue of parent feature. 4. Reports chil