plan
Plan an item in planning: works/<id>/plan.md with its impact table, and its slices in tasks.md, checked, then stopped at the owner's approve. Use when the owner says plan, design, approach, recipe or slices. Pairs with /cook.
- License 许可
- MIT
- 所属仓库
- lamtran8401/nook
- 最近更新
- 2026-10-27
- Stars
- ★ 0
- Forks
- 0
01 前言 Front Matter
- name
- plan
- description
- Plan an item in planning: works/<id>/plan.md with its impact table, and its slices in tasks.md, checked, then stopped at the owner's approve. Use when the owner says plan, design, approach, recipe or slices. Pairs with /cook.
- allowed-tools
- Bash(nook *), Bash(git status *), Bash(git log *), Read, Glob, Grep, Edit, Write
- argument-hint
- [item id]
02 资源文件 5
- 参考文档check.md3.0 KB
- 参考文档example.md10.7 KB
- 参考文档sections.md4.7 KB
- 参考文档slices.md3.1 KB
- 参考文档write.md4.2 KB
03 SKILL.md 正文
!nook item enter plan $ARGUMENTS
Goal: a plan that the owner approves with confidence, and slices that a builder finishes without a question.
The line above took the item, gave its brief with the agents of the plan and their facts, and printed the crafts that the flow of its kind names. Settle the plan before you ask for the approve: a change of substance after it needs nook item replan <id>.
The flow, the question round and the confirm question: ${CLAUDE_PLUGIN_ROOT}/flows/flow.md.
Order
- Start each agent that the brief names under
agents of plan, in the background and in the same turn, but the skeptic: it waits for the plan. The flow of the kind names them, each with its fact. The owner can ask for more in the prompt. - Write the plan:
plan.md, or for size S the## Planofspec.md, or for a fix the## Fixand the## Impactofbug.md. Readwrite.md(this folder) and follow it, with the crafts above. Ask the design choices with a real trade-off, in rounds as the rulequestionssays. - Write the impact table as the craft change-impact says, from
nook item impact <id> --plan. When itsKinds:line names a contract or data, the flow addscontract-analystordata-modeler: start it now. - Cut the slices into
tasks.md, or for size S and for a fix into the## Tasksofspec.mdorbug.md, one### T<n>each: readslices.md(this folder) and follow it. - Check the plan and the slices: read
check.md(this folder), fix each gap, and check again.nook item check <id>imports the slices and must list no gap forapprove. - The skeptic of the brief, for size L: start it with the spec and the plan. Answer each objection that holds in the plan, or put it under Risks with the reason.
- Show the plan and the slices, and ask the confirm question for both.
On "Looks right", report and say: approve: type
/gate approve <id>. Then stop.
An answer kind (spike, research or investigate): no plan.md; its ## Timebox is the plan, and slices only for a proof of concept. Read ${CLAUDE_PLUGIN_ROOT}/skills/requirements/answer.md.
The report
Waits for you: approve: type /gate approve SHOP-12
Plan: works/SHOP-12/plan.md. Slices: T1 bff (S), T2 frontend (S, after T1). ACs covered: 1 to 5. Impact: 3 rows, web runs its checks too. item check: no gap.
Guesses: G1 (low) status order.
Your turn:
1. /gate approve SHOP-12 start the build (recommended)
2. /plan SHOP-12 change the plan with your notes
3. /gate reframe SHOP-12 --reason "<why>" back to the spec
Gotchas
- Each criterion needs a slice that covers it and a test that proves it.
nook item checkreports a criterion with no slice. - A slice touches one area. A change in two areas is two slices, linked by
depends. - Contract first, then the provider, then the consumers. A consumer slice that depends on nothing runs too early.
- The owner confirmed the spec. Edit it only for a real gap and tell the owner. A changed goal needs
nook item reframe. - An agent of the flow that you skip needs its reason in the report: the approve warns about each one that did not run.
- Never run the approve. The owner types
/gate approve <id>in the prompt; the model is denied. - The model starts
/planonly in a yolo run that the owner started; else the owner types it.
A full plan.md and tasks.md for SHOP-12: example.md (this folder).
04 同仓库更多 Skills
yolo
Run an item alone from its state to the owner's accept: the lead runs the phases, records each guess, passes the plan gate with proceed, and stops at a stop rule. Use when the owner types /yolo with an id, a prompt, or nothing.
write-walkthrough
Write walkthrough.md, the explanation of finished work: what works now in plain words, the changed files, where to start reading, the key code, the met criteria, how to try it, the risks. It is the source of the Walkthrough tab of the web app. Use after /qa, or for a question about the code.
wiki-tidy
Find what is wrong in the wiki: broken links, pages with no index line, lines too near the code, stale epic pages, topics with no source, two pages on one topic, adjectives with no example. Fix the mechanical part after one yes; list the rest. Use when the owner says tidy the wiki, or after many pages changed.
wiki-merge
Merge related wiki pages into one complete page: the pages of the features of one process or epic become one page with the flow from end to end. The old pages move to the archive after the owner's yes, and their links point at the new page. Use when the owner says merge these pages, or when wiki-tidy finds pages on one topic.
wiki-ask
Answer a question from the wiki: the index first, then only the pages whose line matches, an answer in a few lines with a link to each page. Use when the owner asks what the wiki says, or asks why or how about a known topic. Not to add a page: wiki-add.
wiki-add
Keep the lesson of a source in the wiki: a page in the shelf business/ or tech/ with its main points, a real example for each, the gotchas and the link of the source; written after the owner's yes. Use when the owner says add this to the wiki, keep this, or gives a PRD, a ticket, notes or an article to keep.