菜单
Use when the user asks to create, file, log, open, draft, refine, decompose, or turn a request, bug, spike, or follow-up into a Linear issue or Linear ticket before work continues.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
| name | creating-linear-issue |
| description | Use when the user asks to create, file, log, open, draft, refine, decompose, or turn a request, bug, spike, or follow-up into a Linear issue or Linear ticket before work continues. |
| argument-hint | [request-or-issue-context] |
Turn a request into a clear Linear issue only after repo discovery, field resolution, source-doc review, user confirmation, and draft approval. Product scope belongs in the issue; implementation sequencing belongs in the later implementation plan.
| Step | Requirement |
|---|---|
| 1 | Classify the request as feature, bug, or spike |
| 2 | Search the codebase and existing Linear issues before asking the user |
| 3 | Resolve project, milestone, assignee, cycle, and any selected-team User Flow requirements using references/field-resolution.md |
| 4 | For selected teams, require and read the matching functional spec before issue creation |
| 5 | Search and read related design docs; record not_applicable when none are related |
| 6 | Use superpowers:brainstorming when a feature is broad, non-trivial, or still has product forks |
| 7 | Use references/bug-intake.md for bug issues |
| 8 | Use references/issue-breakdown.md when the request is too large for one issue |
| 9 | Confirm resolved fields with the user in one question |
| 10 | Show the issue draft and create/update only after approval |
project, milestone, assignee, and cycle unless the user explicitly approves an exception.Studio, Roadmap, and Utilities, do not create an issue without one confirmed User Flow child label and an exact matching docs/functional/<User Flow label>/ folder.For selected-team issues:
docs/design/ by User Flow label, feature name, domain terms, and linked-document titlesFor other teams:
Use references/issue-drafting.md for draft structure and approval content.
The issue body must stay product-level:
\n or escaped checkboxesUse available Linear MCP tools for issue, project, milestone, cycle, label, and comment operations. Retry once on tool failure, then stop and report the exact failing step.
Read references/linear-operations.md for User Flow child-label lookup mechanics. Query User Flow child labels at workspace scope and filter by parent label; do not hard-code label names.
references/field-resolution.md — issue kind, critical fields, selected-team User Flow rule, and confirmation questionreferences/linear-operations.md — Linear MCP tool policy and User Flow child-label lookup mechanicsreferences/issue-drafting.md — draft approval content and issue body templatereferences/issue-breakdown.md — vertical-slice decomposition for large features or parent issuesreferences/bug-intake.md — bug issue intake checks before draftingUse when reviewing a vd-studio pull request as the automated AI PR reviewer (OpenHands pr-review plugin) — judging test coverage for a diff, structuring the review report, or deciding merge readiness.
Use when test quality decisions are needed for new, changed, brittle, missing, or review-requested unit or component tests, including tests-first work, assertion choice, mock boundaries, lifecycle scenarios, or independent test-session handoff.
Use when filing, logging, raising, reporting, or submitting a product issue, feature request, bug, or feedback for the Studio or Utilities product areas in Linear.
Grilling session that challenges your plan against the existing domain model, sharpens terminology, and updates documentation (CONTEXT.md, ADRs) inline as decisions crystallise. Use when user wants to stress-test a plan against their project's language and documented decisions.
Compact the current conversation into a handoff document for another agent to pick up.
Use when asked to implement, fix, build, or work on an existing Linear issue in this repository, and coding should stop before PR creation