activate
Activate a groomed GitHub issue for development — claim it, review it with the owner (scope/acceptance-criteria freshness + backlog overlap, up to 5 issue-specific questions, skippable via owner-instructions), run architect + domain-expert design concurrently then stress-test the result with design-critic, stop for the owner's design choice before generating anything, then OpenSpec explore+propose and stop again for spec approval (Seam 1). Second stage of the flow delivery workflow (see docs/workflow.md). Both stops auto-approvable per the issue's own owner-instruction comment; never implements itself regardless. A `type:docs` issue always skips the design stop; a content-only one (the common case) also skips spec generation, going straight to a lightweight scope + acceptance-criteria review at Seam 1 instead (see docs/workflow.md's Docs fast path). A `type:tech-debt` issue always skips OpenSpec generation and, by default, the owner design-choice wait too — architect still runs but aut
rustyrazorblade · 已有静态检查记录
安装与使用
运行命令前先阅读来源与依赖说明。复制命令不会自动安装或执行。
npx skills add rustyrazorblade/skills --skill activate技能说明
name: activate
description: Activate a groomed GitHub issue for development — claim it, review it with the owner (scope/acceptance-criteria freshness + backlog overlap, up to 5 issue-specific questions, skippable via owner-instructions), run architect + domain-expert design concurrently then stress-test the result with design-critic, stop for the owner's design choice before generating anything, then OpenSpec explore+propose and stop again for spec approval (Seam 1). Second stage of the flow delivery workflow (see docs/workflow.md). Both stops auto-approvable per the issue's own owner-instruction comment; never implements itself regardless. A type:docs issue always skips the design stop; a content-only one (the common case) also skips spec generation, going straight to a lightweight scope + acceptance-criteria review at Seam 1 instead (see docs/workflow.md's Docs fast path). A type:tech-debt issue always skips OpenSpec generation and, by default, the owner design-choice wait too — architect still runs but auto-adopts the Direction already confirmed when the issue was filed, stopping only for a hard dependency, a material deviation, or if the fix can't be done behavior-preserving — then goes to the same lightweight Seam 1 review (see docs/workflow.md's Tech-debt fast path). Marks a hard architect-flagged dependency with both the blocked label and a native GitHub issue dependency.
argument-hint: [issue number — omit to take the highest-priority status:ready issue]
activate — decide the design, spec the work, then stop for approval
You are this issue's issue-manager, running as your own dedicated background session. Take a
status:ready issue and produce an owner-approvable plan on an isolated worktree — normally a
committed OpenSpec change, but a content-only type:docs issue (the common case) skips that
artifact entirely and the plan is just its own scope + acceptance criteria (see step 5), and a
type:tech-debt issue skips it too — its plan is the Direction already confirmed when the issue
was filed, plus whatever existing specified behavior nearby must be preserved (see step 5's
tech-debt branch). Right after claiming, step 1 also reviews the issue with the owner — scope/
acceptance-criteria freshness plus a backlog overlap check, up to five issue-specific questions —
unconditionally, for every issue type; skippable only via the issue's owner instructions for this
run, not one of the stops below. This skill stops for the owner twice in the normal case: once
at step 4 to pick the design, before anything is generated, and again at step 7 — Seam 1 — to
approve
whatever step 5 produced. Step 4's wait is skipped for every type:docs issue (no design to
choose) and, by default, for type:tech-debt too (the architect still runs at step 3, but
auto-adopts the issue's confirmed Direction instead of waiting — see step 4's tech-debt branch);
Step 7 always still applies, in whichever lightweight form matches what was actually produced.
Neither applicable stop is optional by default beyond that; you hand back once the plan is
committed (if applicable) and approved — you do not implement, and you do not start
/spec-flow:implement. The only exception: if the issue's owner instructions at the worktree root
(read fresh at each stop, not just once from your spawn prompt — see agents/issue-manager.md)
explicitly says to auto-approve the design and/or the plan for this run, follow that instead of
waiting — see steps 4 and 7 below for exactly how.
Input: an issue number #N. If omitted, pick the highest-priority status:ready issue that is
unassigned or already assigned to you (gh issue list --label status:ready --json number,title,labels,assignees,subIssuesSummary --limit 100 and choose P0 over P1 …, skipping any issue
assigned to someone else — that's their claim, not yours to take — and skipping any epic
(subIssuesSummary.total > 0; see step 1's epic guard below — pick its highest-priority
status:ready sub-issue instead, or the next status:ready issue if none of its sub-issues
qualify), and confirm the choice with the owner.
Steps
-
Load the issue and claim it.
gh issue view <N> --json number,title,body,labels,assignees,subIssuesSummary. The OpenSpec change for this issue is namedissue-<N>— deterministic, nothing to derive from the title.Announce it clearly, first thing. Before anything else, output a one-line header —
Issue <N>: <title>— as your first visible text. This is what the owner sees first when they attach; with severalissue-managersessions possibly running at once, it's how they tell this tab apart from the others and rename it.Epic guard. If
subIssuesSummary.total > 0, this is a parent/epic issue — its own scope is just a rollup of its sub-issues, nothing to spec or implement directly.scripts/spawn-issue-manager.shalready refuses to spawn against one, so reaching this point on a real epic should be rare (a respawn of a stale session, or activate invoked some other way) — refuse here too rather than claiming it: list its sub-issues (gh issue view <N> --json subIssues --jq '.subIssues.nodes[] | "#\(.number) \(.title)"') and tell the owner to activate one of those instead. Do not proceed to the multi-user guard or claim below.Multi-user guard. Check
assigneesagainst the authenticated user (gh api user --jq .login). If the issue is already assigned to someone else, stop — tell the owner it's claimed and let them pick a different issue or coordinate with whoever has it; do not proceed. Otherwise claim it before doing anything else — hand off to a script that only posts the "claimed" comment on a genuinely fresh claim, not a re-activation (the issue was already assigned to you): re-running this on your own in-flight issue shouldn't repost it every time.${CLAUDE_PLUGIN_ROOT}/scripts/claim-issue.sh <N>