菜单
Break a plan, spec, or findings report into independently-grabbable tracker tickets using vertical-slice tracer bullets. Use when the user wants to turn a plan into tickets, or to decompose a findings report into assignable work.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Regroup the commits since the previous bump (or a given base) into logical commits — one per concern, bump kept last — via scripts/fleet/consolidate-commits.mts. "Consolidate commits" never means squash-to-one; that is squashing-history.
Drives the Cursor Bugbot review-and-fix loop on a PR. Inventories open Bugbot threads, classifies each (real bug / false positive / already fixed), fixes the real ones, replies on the inline thread (never as a detached PR comment), updates the PR title/body if scope shifted, and pushes. Use when reviewing a PR you just authored, after `gh pr create`, or after a new Bugbot pass on an existing PR.
Reviews the current branch against a base ref using multiple AI backends. Runs a Workflow that streams the diff through discovery, discovery-secondary, remediation, and adversarial-verify stages, routing each stage to the available agents (codex, claude, opencode, kimi, …) and gracefully skipping any backend that isn't installed. Writes a markdown findings report under docs/. Use when preparing or updating a PR, before merging a feature branch, or when wanting an independent second opinion from a different agent.
Full repo onboarding wizard. Orchestrates all setup concerns for a new engineer or a fresh clone — API token, OS keychain, shell rc bridge, native messaging host, security tools, and repo-specific initialization. Invoke with /setup-repo.
Propagate a wheelhouse template change to every fleet repo. Packages the canonical fleet-repo list, the FLEET_SYNC=1 sentinel pattern, the worktree-per-repo loop, push-direct + PR-fallback, and worktree-cleanup that survives mid-loop crashes. Use when a wheelhouse template SHA needs to land in every fleet repo, or when batching multiple template SHAs into one cascade wave. Tool-version pin propagation is the wheelhouse pipeline's job (scripts/repo/pipeline.mts), not this skill's.
Manages git worktrees per the fleet's parallel-Claude-sessions rule. Creates new task-worktrees, fans out one worktree per open PR for parallel review, and prunes spent worktrees that have nothing left to land — clean trees whose branch was deleted upstream OR is fully merged into the remote default branch. Use when starting a task that needs an isolated working tree, when reviewing every open PR locally without disturbing the primary checkout, or when cleaning up after merges.
| name | decomposing-tickets |
| description | Break a plan, spec, or findings report into independently-grabbable tracker tickets using vertical-slice tracer bullets. Use when the user wants to turn a plan into tickets, or to decompose a findings report into assignable work. |
| user-invocable | true |
Break a plan into tracer-bullet tickets — each a thin vertical slice through
ALL layers end-to-end (schema → API → UI → tests), demoable on its own — never a
horizontal slice of one layer. Adapted from mattpocock/to-tickets. The natural
output of grilling-plan → authoring-spec → this.
Work from the conversation context (or fetch the referenced issue/plan). Explore
the codebase so issue titles use the project's domain vocabulary
(rg the affected modules). Look for prefactors — "make the change easy, then
make the easy change."
Each slice: a narrow but COMPLETE path through every layer, verifiable on its own, with prefactoring done first. For a findings report, one slice per true-positive finding (or a tight cluster), each independently landable.
Present the breakdown as a numbered list — title, blocked by (which slices must land first), user stories covered. Ask: is the granularity right? are the dependencies correct? merge/split any? Iterate until approved.
Every issue body is a public-facing surface. Run the prose skill over each body
and apply prose-style-and-doctrine:
lead with the point, no throat-clearers/filler, evidence over assertion, state the
positive directly. Public-surface hygiene
(public-surface-hygiene):
no real customer/company name, no private repo, no Linear ref, and never a bare
#N in the prose (it auto-links to an unrelated issue) — write the full URL or
org/repo#N.
Publish blockers first so you can reference real issue identifiers in each
"Blocked by" field. Default tracker is GitHub via gh issue create; use the
Linear MCP save_issue tool if the repo tracks work in Linear. Apply the
ready-for-agent triage label unless told otherwise. Publishing is mutating +
outward-facing — confirm the tracker + label before the first create.
Every approved slice is published in dependency order with real "Blocked by"
references, each body has passed the prose + doctrine pass, and no body leaks a
private name or bare #N.
