meaningful-linear-issueslisted

Create complete, analytics-ready Linear issues in ONE pass — resolve the right project (never guess it), and proactively fill the metadata that's technically optional but matters for planning/analytics: priority, estimate, labels (a Type + an Area from the team's existing taxonomy), milestone, assignee, cycle, and relations. Use when asked to 'create/file/open a Linear issue', 'log a ticket', 'add this to Linear', 'make an issue for X', or before any Linear `save_issue` that **creates** an issue or **backfills** missing metadata on a bare one — so the user doesn't have to come back and ask for the labels/estimate/project a second time, and so an issue doesn't land in the wrong project. NOT for routine field edits (status changes, reassignments) — those are also `save_issue` but don't need this.
stealth-engine/skills · ★ 2 · AI & Automation · score 76

Install: claude install-skill stealth-engine/skills

# Meaningful Linear issues A good issue is **not** just a good description — that's the easy half. The half agents skip is the **metadata** that makes Linear actually work as a planning tool: estimates feed cycle velocity, labels feed breakdowns, milestones feed roadmaps, the project feeds everything. Those fields are *optional in the API*, so agents leave them blank and the user has to come back and ask again. **Flip the default: metadata is opt-OUT, not opt-in.** Resolve and fill it **before** calling `save_issue`, in one pass — propose concrete values, don't omit. ## Cardinal rule: never guess the project The single worst failure is dropping an issue into the **wrong/random project**. Resolve the project in this order — **stop at the first that's certain**: 1. **Context** — the issue's repo/area maps to a known project; the user named it; a sibling issue you're relating to has one. 2. **Confirm** — call [`list_projects`](#discover-valid-values) and match by name; if one clearly fits, state which and proceed. 3. **Ask** — if it's still ambiguous, **ask the user which project** rather than picking one. A missing project is recoverable; a wrong one quietly pollutes the wrong roadmap. Never pass a `project` you inferred from vibes. Team is required too — usually unambiguous from the project, but resolve it the same way. ## The one-pass workflow 1. **Discover** what's available (only what you don't already know): projects, the team's label taxonomy, miles