菜单
Create a Linear issue for the Personal Agent project with the correct team, state, and label policy. Use when the user asks to create, file, open, or draft a Linear issue/ticket. Do not invoke for reading or updating existing issues.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Use in the master session to integrate a ready PR — analyze (code-review + security-review), doc-drift check, merge, ask before deploy, verify live, close Linear, update MASTER_PLAN.
Use after /clear in the explore session (cc-explore) to rebuild full project situational awareness from durable sources — observer/strategist role, read-only, never actuate. All of master's vision, none of its hands; the deliberation seat where deep strategy/methodology thinking happens off master's context.
Use in the adr session (Opus) to explore an idea with the owner and — if it earns it — produce a complete ADR. Discuss/explore first, write, iterate with codex review, open ADR PR, then file sequenced implementation tickets. An ADR is a possible outcome, not a mandate. Never touches src/ or merges.
Use in the build session to ship a Linear FRE ticket from Approved to a master-ready PR (CI green + any bounce resolved) — fresh-start reset, plan with risk-tiered codex review (reviewer, not co-author), TDD, docs, PR, then self-complete via watcher/master pokes. Never merges or deploys.
Owner-invoked before resetting (/clear-ing) a session. Verifies a safe reset boundary, writes the session-delta artifact (LAST_SESSION.md) so the next session inherits this session's decisions, distills standing facts into memory, checkpoints MASTER_PLAN, and emits a go/no-go verdict. The safe wind-down bookend to prime-master.
Use after /clear in the master session to rebuild the guardian snapshot from durable sources — current state (1-7) then target (8) then process (9). Never from prior conversation.
| name | linear-issue-create |
| description | Create a Linear issue for the Personal Agent project with the correct team, state, and label policy. Use when the user asks to create, file, open, or draft a Linear issue/ticket. Do not invoke for reading or updating existing issues. |
| disable-model-invocation | true |
Create a Linear issue that conforms to the Linear Implement Gate policy in .claude/CLAUDE.md:
New == Needs Approval. Implement == Approved.
| Field | Value |
|---|---|
| Team | FrenchForest |
| State | Needs Approval (state — not a label) |
| Labels | PersonalAgent + exactly one tier label |
| Tier label (pick one) | Tier-1:Opus · Tier-2:Sonnet · Tier-3:Haiku |
Use the routing policy from .claude/MODEL_ROUTING_POLICY.md:
Ask the user which tier if it isn't obvious from the description.
mcp__claude_ai_Linear__list_teams → find FrenchForestmcp__claude_ai_Linear__list_issue_labels → find IDs for PersonalAgent + chosen tier labelmcp__claude_ai_Linear__list_issue_statuses → find state ID for Needs Approvalmcp__claude_ai_Linear__save_issue with team, state, label IDs, title, description.Needs Approval — implementation is blocked until they move it to Approved.Needs Approval label (the policy uses state, not label).Approved yourself. Only the user does that.FrenchForest.✅ Created FRE-XXX — <title>
State: Needs Approval
Labels: PersonalAgent, Tier-N:Model
URL: https://linear.app/...
Implementation is gated until you move it to Approved.