tasklisted

# Task The **first step of every task.** Turns a GitHub issue into a ready-to-work branch, kicks off the mandatory alignment grill, and later keeps the branch current before a PR. Invoke this skill instead of calling the scripts by hand — it orchestrates them. All git actions run from the repo root; the scripts need PowerShell 7 (`pwsh`). ## Parameters ```text $ARGUMENTS ``` - **issue** — the GitHub issue number, e.g. `142`. Optional if a description is given directly. - **type** (optional) — `feature` | `bug` | `hotfix`. If omitted, inferred from the issue's labels (a `bug` label → `bug`), defaulting to `feature`. Hotfix is always an explicit human call and is never inferred. Typical invocation: `/task 142 feature`, or just `/task 142`. ## Prerequisites The [`gh` CLI](https://cli.github.com), authenticated (`gh auth login`). No tokens, config files, or environment variables of your own — `gh` owns the credential. The tracker is **optional**. With no issue to work from, pass a description straight through and everything below still applies: ```powershell ./scripts/new-task-branch.ps1 -Description "Add upload retry" -Type feature ``` ## 1. Intake — read the issue ```powershell gh issue view 142 --json number,title,body,labels ``` Use the title and body as the source of truth. If the user also supplied a description, prefer theirs only when they say so; otherwise use the issue title. This text seeds `specs/<feature>/brief.md` when the change goes through the Spec Ki