菜单
Turn a feature request into a concrete plan — scope, approach, affected files, a test plan mapped to acceptance criteria, and out-of-scope — before any code is written. Use when the user describes new work, asks to design or spec something, or says "plan this" / "how would you build X".
用 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 | plan-feature |
| description | Turn a feature request into a concrete plan — scope, approach, affected files, a test plan mapped to acceptance criteria, and out-of-scope — before any code is written. Use when the user describes new work, asks to design or spec something, or says "plan this" / "how would you build X". |
| model | opus |
| effort | high |
| allowed-tools | ["Read","Grep","Glob","Bash"] |
| argument-hint | <feature request or ticket id> |
| triggers | ["plan this","how would you build","design a","spec out","what's the approach"] |
| tags | ["planning","design","spec","pipeline"] |
Produce a plan good enough that implementation is mechanical. This is the first
pipeline step (plan → track → implement → review → pr). Planning is reasoning-
heavy — run it on a strong model at high effort.
node "${CLAUDE_PLUGIN_ROOT}/hooks/memory.mjs" reply "<feature keywords>"
Don't re-plan something already decided — build on it.
Create or update the ticket and mark planning done:
# create a ticket if this is new work (prints the id, e.g. HZ-1)
node "${CLAUDE_PLUGIN_ROOT}/hooks/pipeline.mjs" new "<feature title>" --type story
# record the plan as a durable decision + mark the step done
node "${CLAUDE_PLUGIN_ROOT}/hooks/memory.mjs" keep "<one-line plan summary + key decision>" --kind decision --tags plan
node "${CLAUDE_PLUGIN_ROOT}/hooks/pipeline.mjs" step <ticket-id> plan done --note "<short>"
Present the plan, the ticket id, and the next step: track-work to break it down, or implement to build it. Under ship, return a one-line summary and the ticket id.