菜单
Umbrella skill that drives the full happy delivery pipeline end-to-end for one request or ticket — plan → track → implement → review → open-pr — stopping before merge. Use when the user wants a change shipped with one command, or to resume a ticket's pipeline from where it left off.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Run a bounded change → verify → fix cycle until an objective check passes (tests green, lint clean, build/type-check ok) or a hard iteration cap is hit. Use for any task that needs repeated attempts against a verifiable signal instead of a single one-shot edit.
Review code for behavior-preserving simplification — collapse duplication, remove dead code and over-engineering, cut verbose patterns down to idiomatic ones. Use when code is longer or more complex than it needs to be, or the user asks to simplify, shorten, refactor, or clean up.
Implement a planned ticket on its own branch using test-first development, updating docs as part of the change, looping change→verify→fix until the suite is green. Use when a ticket has a plan and is ready to build, or the user says "implement X" / "build the ticket" / "make it pass".
Use to store durable context (decisions, facts, preferences, todos, summaries) and to recall or reply from it across sessions. Load when something worth remembering appears, or when the user asks what you were doing, what was decided, or to continue prior work.
Choose the right model and effort per task phase and apply it when dispatching subagents — strong model + high effort for planning and review, a cheaper model + lower effort for mechanical execution. Use when a task splits into plan / execute / review phases or you're spawning subagents.
Push a reviewed ticket branch and open a pull request with a structured title and body, after review-changes has passed. Use when a ticket is reviewed and ready to ship, or the user says "open a PR" / "create the pull request". Stops at opening the PR — never merges.
| name | ship |
| description | Umbrella skill that drives the full happy delivery pipeline end-to-end for one request or ticket — plan → track → implement → review → open-pr — stopping before merge. Use when the user wants a change shipped with one command, or to resume a ticket's pipeline from where it left off. |
| model | opus |
| effort | high |
| allowed-tools | ["Read","Edit","Write","Grep","Glob","Bash","Task"] |
| argument-hint | <request or ticket id> |
| triggers | ["ship this","take this end to end","run the pipeline","build and open a pr"] |
| tags | ["pipeline","orchestration","delivery","ship"] |
Drive one change through the whole pipeline. You orchestrate the step skills; you do not do their work inline. Stop at the PR — a human merges.
Pipeline order: plan-feature → track-work → implement → review-changes → open-pr.
node "${CLAUDE_PLUGIN_ROOT}/hooks/memory.mjs" reply "<keywords>"
node "${CLAUDE_PLUGIN_ROOT}/hooks/pipeline.mjs" list
HZ-3) → resume that ticket.The pipeline store, not your recollection, decides what runs next:
node "${CLAUDE_PLUGIN_ROOT}/hooks/pipeline.mjs" next <ticket-id> # -> plan | track | implement | review | pr | complete
Map the result to the skill and run it:
next | Run skill |
|---|---|
plan | plan-feature |
track | track-work (skip for a single small ticket — mark it done and move on) |
implement | implement |
review | review-changes |
pr | open-pr |
complete | go to Finish |
Re-check next after every step. A step left in_progress/failed is simply
re-run — the step skill reconciles reality itself.
Follow each step skill to completion as its coordinator (load it and do it, or dispatch a subagent for it). Apply per-role model + effort via model-router: plan/review on the strong model at high effort, implement on the mid model. Keep what you carry between steps tiny — the ticket id and the last step's status are enough; everything else is in the store and memory.
next, continue.pipeline show <id>), and how to resume (ship <ticket-id>). Do not
paper over a failed review or a red suite.Report the per-step status (pipeline show <id>) and the PR URL. End with: the
PR is open and ready for human review + merge. On a stopped pipeline, give the
resume command and what needs fixing.