new-featurelisted

# Starting a New Feature This skill creates the run folder, writes the plan, and wires everything to Linear before a single line of code is written. ## Step 0 — Identify the Linear issue The primary Linear interface for skills is **`node tools/linear-cli.mjs`** — a small REST/GraphQL wrapper that works in any process (interactive or background) using `LINEAR_API_KEY` from `.env.local`. It does NOT depend on a Linear MCP, which is unreliable in background sessions. If the user provided an issue ID (e.g. via `/new-feature ACM-42`), fetch it: ```bash node tools/linear-cli.mjs get ACM-42 ``` If the user didn't provide an ID, list unassigned backlog issues and ask which one to work on: ```bash node tools/linear-cli.mjs list --team {TEAM_NAME} --state Backlog --unassigned --limit 20 ``` Capture from the `get` output: - `ISSUE_ID` — e.g. `ACM-42` (the `identifier` field) - `ISSUE_URL` — the `url` field - `ISSUE_TITLE` + `ISSUE_DESCRIPTION` — for the plan - `SHORT_NAME` — 2–4 word kebab-case slug derived from the title - `AGENT_IDENTITY` — read from `git config user.email` ## Step 0.5 — Lock the issue (claim-before-work) **Critical for parallel agents — do this before writing any files.** ```bash node tools/linear-cli.mjs claim ACM-42 --email "$(git config user.email)" ``` The CLI does the race-safe sequence internally: read assignee → abort if owned by another email (exit code 2) → write assignee + In Progress → re-read to verify ownership → abort again if a race was los