[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7F5322KDCWDZ1AH25PJDQJC":3,"skill-same:01M7F5322KDCWDZ1AH25PJDQJC":68},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":26,"commitSha":27,"skillDirectory":28,"forksCount":14,"repositoryHtmlUrl":29,"repositoryHomepageUrl":6,"ownerHtmlUrl":30,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":31,"install":32,"resources":45},"01M7F5322KDCWDZ1AH25PJDQJC","plan",null,"Plan an item in planning: works\u002F\u003Cid>\u002Fplan.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 \u002Fcook.","lamtran8401\u002Fnook","lamtran8401","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F91517229?v=4","01M7F5172CY814PXRBJG6TWAAC","Trần Vũ Lam","01M7F5173D7DJEW5XS3V04KC1V",0,"MIT","https:\u002F\u002Fgithub.com\u002Flamtran8401\u002Fnook\u002Fblob\u002Fmain\u002Fplugin\u002Fskills\u002Fplan\u002FSKILL.md",[],[],"2026-11-16 10:05:34",false,"---\nname: plan\ndescription: \"Plan an item in planning: works\u002F\u003Cid>\u002Fplan.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 \u002Fcook.\"\nargument-hint: \"[item id]\"\nallowed-tools: Bash(nook *), Bash(git status *), Bash(git log *), Read, Glob, Grep, Edit, Write\n---\n\n!`nook item enter plan $ARGUMENTS`\n\nGoal: a plan that the owner approves with confidence, and slices that a builder finishes without a question.\nThe 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 \u003Cid>`.\nThe flow, the question round and the confirm question: `${CLAUDE_PLUGIN_ROOT}\u002Fflows\u002Fflow.md`.\n\n## Order\n1. 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.\n2. Write the plan: `plan.md`, or for size S the `## Plan` of `spec.md`, or for a fix the `## Fix` and the `## Impact` of `bug.md`. Read `write.md` (this folder) and follow it, with the crafts above. Ask the design choices with a real trade-off, in rounds as the rule `questions` says.\n3. Write the impact table as the craft change-impact says, from `nook item impact \u003Cid> --plan`. When its `Kinds:` line names a contract or data, the flow adds `contract-analyst` or `data-modeler`: start it now.\n4. Cut the slices into `tasks.md`, or for size S and for a fix into the `## Tasks` of `spec.md` or `bug.md`, one `### T\u003Cn>` each: read `slices.md` (this folder) and follow it.\n5. Check the plan and the slices: read `check.md` (this folder), fix each gap, and check again. `nook item check \u003Cid>` imports the slices and must list no gap for `approve`.\n6. 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.\n7. Show the plan and the slices, and ask the confirm question for both.\n   On \"Looks right\", report and say: approve: type `\u002Fgate approve \u003Cid>`. Then stop.\n\nAn 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}\u002Fskills\u002Frequirements\u002Fanswer.md`.\n\n## The report\n```\nWaits for you: approve: type \u002Fgate approve SHOP-12\nPlan: works\u002FSHOP-12\u002Fplan.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.\nGuesses: G1 (low) status order.\nYour turn:\n  1. \u002Fgate approve SHOP-12   start the build   (recommended)\n  2. \u002Fplan SHOP-12   change the plan with your notes\n  3. \u002Fgate reframe SHOP-12 --reason \"\u003Cwhy>\"   back to the spec\n```\n\n## Gotchas\n- Each criterion needs a slice that covers it and a test that proves it. `nook item check` reports a criterion with no slice.\n- A slice touches one area. A change in two areas is two slices, linked by `depends`.\n- Contract first, then the provider, then the consumers. A consumer slice that depends on nothing runs too early.\n- The owner confirmed the spec. Edit it only for a real gap and tell the owner. A changed goal needs `nook item reframe`.\n- An agent of the flow that you skip needs its reason in the report: the approve warns about each one that did not run.\n- Never run the approve. The owner types `\u002Fgate approve \u003Cid>` in the prompt; the model is denied.\n- The model starts `\u002Fplan` only in a yolo run that the owner started; else the owner types it.\n\nA full `plan.md` and `tasks.md` for SHOP-12: `example.md` (this folder).\n","!`nook item enter plan $ARGUMENTS`\n\nGoal: a plan that the owner approves with confidence, and slices that a builder finishes without a question.\nThe 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 \u003Cid>`.\nThe flow, the question round and the confirm question: `${CLAUDE_PLUGIN_ROOT}\u002Fflows\u002Fflow.md`.\n\n## Order\n1. 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.\n2. Write the plan: `plan.md`, or for size S the `## Plan` of `spec.md`, or for a fix the `## Fix` and the `## Impact` of `bug.md`. Read `write.md` (this folder) and follow it, with the crafts above. Ask the design choices with a real trade-off, in rounds as the rule `questions` says.\n3. Write the impact table as the craft change-impact says, from `nook item impact \u003Cid> --plan`. When its `Kinds:` line names a contract or data, the flow adds `contract-analyst` or `data-modeler`: start it now.\n4. Cut the slices into `tasks.md`, or for size S and for a fix into the `## Tasks` of `spec.md` or `bug.md`, one `### T\u003Cn>` each: read `slices.md` (this folder) and follow it.\n5. Check the plan and the slices: read `check.md` (this folder), fix each gap, and check again. `nook item check \u003Cid>` imports the slices and must list no gap for `approve`.\n6. 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.\n7. Show the plan and the slices, and ask the confirm question for both.\n   On \"Looks right\", report and say: approve: type `\u002Fgate approve \u003Cid>`. Then stop.\n\nAn 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}\u002Fskills\u002Frequirements\u002Fanswer.md`.\n\n## The report\n```\nWaits for you: approve: type \u002Fgate approve SHOP-12\nPlan: works\u002FSHOP-12\u002Fplan.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.\nGuesses: G1 (low) status order.\nYour turn:\n  1. \u002Fgate approve SHOP-12   start the build   (recommended)\n  2. \u002Fplan SHOP-12   change the plan with your notes\n  3. \u002Fgate reframe SHOP-12 --reason \"\u003Cwhy>\"   back to the spec\n```\n\n## Gotchas\n- Each criterion needs a slice that covers it and a test that proves it. `nook item check` reports a criterion with no slice.\n- A slice touches one area. A change in two areas is two slices, linked by `depends`.\n- Contract first, then the provider, then the consumers. A consumer slice that depends on nothing runs too early.\n- The owner confirmed the spec. Edit it only for a real gap and tell the owner. A changed goal needs `nook item reframe`.\n- An agent of the flow that you skip needs its reason in the report: the approve warns about each one that did not run.\n- Never run the approve. The owner types `\u002Fgate approve \u003Cid>` in the prompt; the model is denied.\n- The model starts `\u002Fplan` only in a yolo run that the owner started; else the owner types it.\n\nA full `plan.md` and `tasks.md` for SHOP-12: `example.md` (this folder).\n",{"name":5,"description":7,"allowed-tools":24,"argument-hint":25},"Bash(nook *), Bash(git status *), Bash(git log *), Read, Glob, Grep, Edit, Write","[item id]","main","0b3b58696520a442b4b4f87c1c5a5ac760c03120","plugin\u002Fskills\u002Fplan","https:\u002F\u002Fgithub.com\u002Flamtran8401\u002Fnook","https:\u002F\u002Fgithub.com\u002Flamtran8401","2026-10-27 20:01:54",{"source":8,"skillName":5,"commands":33,"prompt":43,"zipAvailable":44},[34,37,40],{"tool":35,"command":36},"npx","npx skills add lamtran8401\u002Fnook --skill plan",{"tool":38,"command":39},"bunx","bunx skills add lamtran8401\u002Fnook --skill plan",{"tool":41,"command":42},"pnpm","pnpm dlx skills add lamtran8401\u002Fnook --skill plan","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Flamtran8401\u002Fnook\u002Fblob\u002Fmain\u002Fplugin\u002Fskills\u002Fplan\u002FSKILL.md",true,[46,52,56,60,64],{"path":47,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":50,"sourceHtmlUrl":51},"check.md","REFERENCE","参考文档",3068,"https:\u002F\u002Fgithub.com\u002Flamtran8401\u002Fnook\u002Fblob\u002Fmain\u002Fplugin\u002Fskills\u002Fplan\u002Fcheck.md",{"path":53,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":54,"sourceHtmlUrl":55},"example.md",10983,"https:\u002F\u002Fgithub.com\u002Flamtran8401\u002Fnook\u002Fblob\u002Fmain\u002Fplugin\u002Fskills\u002Fplan\u002Fexample.md",{"path":57,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":58,"sourceHtmlUrl":59},"sections.md",4762,"https:\u002F\u002Fgithub.com\u002Flamtran8401\u002Fnook\u002Fblob\u002Fmain\u002Fplugin\u002Fskills\u002Fplan\u002Fsections.md",{"path":61,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":62,"sourceHtmlUrl":63},"slices.md",3189,"https:\u002F\u002Fgithub.com\u002Flamtran8401\u002Fnook\u002Fblob\u002Fmain\u002Fplugin\u002Fskills\u002Fplan\u002Fslices.md",{"path":65,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":66,"sourceHtmlUrl":67},"write.md",4309,"https:\u002F\u002Fgithub.com\u002Flamtran8401\u002Fnook\u002Fblob\u002Fmain\u002Fplugin\u002Fskills\u002Fplan\u002Fwrite.md",[69,76,83,90,97,104],{"skillNo":70,"name":71,"nameZh":6,"description":72,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":73,"categories":74,"keywords":75,"publishedAt":19},"01M7F55NA9ZJEBZ27S3PN5ZN0J","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 \u002Fyolo with an id, a prompt, or nothing.","https:\u002F\u002Fgithub.com\u002Flamtran8401\u002Fnook\u002Fblob\u002Fmain\u002Fplugin\u002Fskills\u002Fyolo\u002FSKILL.md",[],[],{"skillNo":77,"name":78,"nameZh":6,"description":79,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":80,"categories":81,"keywords":82,"publishedAt":19},"01M7F55GE7WPQCSP3K44BEY0TE","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 \u002Fqa, or for a question about the code.","https:\u002F\u002Fgithub.com\u002Flamtran8401\u002Fnook\u002Fblob\u002Fmain\u002Fplugin\u002Fskills\u002Fwrite-walkthrough\u002FSKILL.md",[],[],{"skillNo":84,"name":85,"nameZh":6,"description":86,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":87,"categories":88,"keywords":89,"publishedAt":19},"01M7F55A7M9W0D5340Y4A8YFB7","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.","https:\u002F\u002Fgithub.com\u002Flamtran8401\u002Fnook\u002Fblob\u002Fmain\u002Fplugin\u002Fskills\u002Fwiki-tidy\u002FSKILL.md",[],[],{"skillNo":91,"name":92,"nameZh":6,"description":93,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":94,"categories":95,"keywords":96,"publishedAt":19},"01M7F555A8JJHX4Q61Q06B6DBS","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.","https:\u002F\u002Fgithub.com\u002Flamtran8401\u002Fnook\u002Fblob\u002Fmain\u002Fplugin\u002Fskills\u002Fwiki-merge\u002FSKILL.md",[],[],{"skillNo":98,"name":99,"nameZh":6,"description":100,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":101,"categories":102,"keywords":103,"publishedAt":19},"01M7F551S3NHQ0JVT0KGM36WPQ","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.","https:\u002F\u002Fgithub.com\u002Flamtran8401\u002Fnook\u002Fblob\u002Fmain\u002Fplugin\u002Fskills\u002Fwiki-ask\u002FSKILL.md",[],[],{"skillNo":105,"name":106,"nameZh":6,"description":107,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":108,"categories":109,"keywords":110,"publishedAt":19},"01M7F54XC5YQK6KVXJVPZ6NDM4","wiki-add","Keep the lesson of a source in the wiki: a page in the shelf business\u002F or tech\u002F 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.","https:\u002F\u002Fgithub.com\u002Flamtran8401\u002Fnook\u002Fblob\u002Fmain\u002Fplugin\u002Fskills\u002Fwiki-add\u002FSKILL.md",[],[]]