메뉴
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.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Use 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.
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
Use when the user wants to add a roadmap item, submit a roadmap request, propose a product roadmap candidate, or log RO-team roadmap intake in Linear. Not for generic Linear issue creation, bug reports, or implementation tickets.
| name | creating-product-issues |
| description | 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. |
| argument-hint | [request-or-issue-context] |
Turn a product request into a clear Linear issue in the Studio or Utilities team only, after repo discovery, field resolution, source-doc review, user confirmation, and draft approval. The team owner is resolved from a static team-to-owner map. No project, milestone, or cycle is assigned.
creating-linear-issue for those.| 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 team (must be Studio or Utilities), User Flow child label, and owner from the static team-to-owner map in references/field-resolution.md |
| 4 | 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 ../creating-linear-issue/references/bug-intake.md for bug issues |
| 8 | Use ../creating-linear-issue/references/issue-breakdown.md when the request is too large for one issue |
| 9 | Confirm resolved fields (team, owner, User Flow label) with the user in one question |
| 10 | Show the issue draft and create/update only after approval |
Studio or Utilities. Explain that this skill files product issues only into Studio or Utilities, and ask the user to email ss@acceleratedata.ai if the right target is unclear.project, milestone, or cycle on the filed issue.For all issues filed by this skill (both Studio and Utilities require it):
docs/design/ by User Flow label, feature name, domain terms, and linked-document titlesShow the full draft before creating or updating the issue. Include:
not_applicableCreate or update the Linear issue only after user approval.
## Problem
...
## Goal
...
## Non-goals
- ...
## Acceptance Criteria
- [ ] ...
## Risks
- ...
## Test Notes
- ...
Include the functional spec path and related design doc paths in the description so triage and implementation can trace source context. Do not include project, milestone, or cycle fields.
Use available Linear MCP tools for issue, 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 and owner-by-email lookup mechanics.
Studio or Utilities.project, milestone, or cycle fields (the skill explicitly does not).references/field-resolution.md — issue kind, team allowlist, static team-to-owner map, User Flow rule, and confirmation questionreferences/linear-operations.md — Linear MCP tool policy, User Flow child-label lookup, and owner-by-email lookup../creating-linear-issue/references/issue-drafting.md — draft approval content and issue body template (shared with creating-linear-issue)../creating-linear-issue/references/issue-breakdown.md — vertical-slice decomposition (shared)../creating-linear-issue/references/bug-intake.md — bug issue intake checks (shared)