linear-issue-craftlisted

# Linear Issue Craft A portable issue-writing style. Every pattern in this skill is grounded in real shipped issues — see `references/06-canonical-examples.md` for verbatim source material. ## When this skill applies Invoke when the user wants to create or polish a Linear issue and you have any signal that they want this style. Skip when the user explicitly asks for a different style or templates from another team. ## The three issue archetypes Every issue is one of three shapes. Identify the archetype first — it determines title pattern, body sections, and labels. | Archetype | When to use | Title shape | Body sections | |---|---|---|---| | **Epic** | Strategic surface, 2–8 child stories, shared infra/domain | `Epic: <Domain>` | Goal · Outcomes · Out of scope · Stories under this epic | | **Story** | One PR, one acceptance test, one service/surface | imperative verb + concrete deliverable, or `<Role> — <Capability>` | (epic backlink) · User Story · Problem · Solution · Requirements · Evaluation | | **Hardening** | Multiple vulnerabilities/bugs in one file/service | `Harden <file.ts>: <symptom1>, <symptom2>, <symptom3>` | Summary · Issues (numbered, each with **Fix:**) | If a request doesn't fit one of these three, **stop and decompose** before writing. A "let's also rework X while we're at it" is a sibling story, not a bolted-on requirement. ## Decision flow ``` ┌──────────────────────────────┐ │ Is the request scoped to one│ │