[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7DX0ECWW3SANP6C6BYRVRRB":3,"skill-same:01M7DX0ECWW3SANP6C6BYRVRRB":48},{"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":25,"commitSha":26,"skillDirectory":27,"forksCount":28,"repositoryHtmlUrl":29,"repositoryHomepageUrl":6,"ownerHtmlUrl":30,"ownerBlogUrl":31,"ownerDescription":32,"updatedAt":33,"install":34,"resources":47},"01M7DX0ECWW3SANP6C6BYRVRRB","plan",null,"Open a dossier and write its plan with the operator, then get it checked by a fresh agent before any build. Invoke when the user says \"ds:plan\", \"start a dossier\", \"plan this\", \"grill me\" in a repo with `.scratchpad\u002Fdossier\u002F`, or when work needs more than one commit.","raisedadead\u002Fclaude-code-plugins","raisedadead","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F1884376?v=4","01M72WC4WYRJGZ2CXMCSF7B6VG","Mrugesh Mohapatra","01M72WC4XJTNHQ0D89QPG2H0W4",3,"ISC","https:\u002F\u002Fgithub.com\u002Fraisedadead\u002Fclaude-code-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fdossier\u002Fskills\u002Fplan\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: plan\ndescription: Open a dossier and write its plan with the operator, then get it checked by a fresh agent before any build. Invoke when the user says \"ds:plan\", \"start a dossier\", \"plan this\", \"grill me\" in a repo with `.scratchpad\u002Fdossier\u002F`, or when work needs more than one commit.\nargument-hint: \u003Cslug> [goal sentence]\n---\n\n# ds:plan\n\nYou are the Chief of Staff. You ask the questions and write the plan text. The `ds` commands do every step that gives the same result each time. Do not copy lines, count, rename or move rows by hand.\n\n## Steps\n\n1. `ds new \u003Cslug>` prints the plan file. Fill it in this order. `FORMAT.md` in this plugin has the exact shape.\n   - **Goal**: the operator's words, quoted.\n   - **Scope**: one `- in:` line and one `- out:` line.\n   - **Decisions**: grill the operator with the `whetstone:grill` method: decision blocks, the recommendation first, a later round for an answer that adds or removes questions, and a fresh ask when an answer changes a premise. Look up each fact with a `gatherer` agent. Write one numbered line per decision, `\u003Cquestion> — \u003Canswer> · \u003Cdate>`.\n     - \"Discuss more\" on a decision: answer it `split into \u003Cn>, \u003Cm>` and ask the parts as new numbered decisions.\n     - A decision only someone outside the room can answer: write the `whetstone:grill` questionnaire to `questionnaire-\u003Cn>.md` in the dossier folder (`ds path`), answer the decision `waits on \u003Cwho>: \u003Cquestionnaire path>`, and add a row for it with `ds add \"\u003Ctitle>\" --who H --state wait`.\n     - Then add `confirmed: \"\u003Cthe operator's words>\"`.\n   - **Rows**: add each with `ds add \"\u003Ctitle>\"`, never by hand, before any section names it. Put row detail under `## Notes` as `### O\u003CN>`.\n   - **Checks**: each check is a command that fails today and passes when the work is done. A guard check passes today and must stay green.\n   - **Edge cases**: `- \u003Ccase> → \u003Crow or check>`.\n   - **Commits**: the planned commits, with subject, rows and paths. Plan few commits, and keep each one whole.\n2. Run `ds lint` until it prints `LINT: OK`.\n3. Run `ds check --baseline` until it prints `BASELINE: OK`.\n4. Run `ds pack plan`. In one message, spawn one `plan-checker` agent with the pack path, and, on the first check only, the subtraction pass: `whetstone:whetstone-doubter` with the subtraction mission of `whetstone:doubt-pass`, the pack as the artifact, Goal and Scope as the contract, and `model` set to this session's model family. The plan checker writes a findings file that ends `VERDICT: PASS` or `VERDICT: CHANGES`.\n5. Run `ds record plan \u003Cfindings>`.\n   - Exit 0: the plan check passed.\n   - Exit 1: change the plan for each finding, then repeat steps 2 to 5.\n   - Exit 3: this was the second CHANGES. Show the findings to the operator and stop.\n6. The subtraction pass: show its cuts to the operator in one decision block, and take only the cuts the operator picks. Then `ds log \"subtract: \u003Cits first line>; took \u003Ccut numbers or none>\"`; without Whetstone, `ds log \"subtract: skipped, no Whetstone\"`. Until that line is in the worklog, `ds handoff` asks for the cuts. A taken cut changes the plan, so repeat steps 2 to 5 without the subtraction pass.\n\nEnd the turn with the lines `ds handoff` prints.\n\nDiscovery is the long part of the work. Leave no guess in the plan: a surprise that a review finds later is a gap in this step.\n","# ds:plan\n\nYou are the Chief of Staff. You ask the questions and write the plan text. The `ds` commands do every step that gives the same result each time. Do not copy lines, count, rename or move rows by hand.\n\n## Steps\n\n1. `ds new \u003Cslug>` prints the plan file. Fill it in this order. `FORMAT.md` in this plugin has the exact shape.\n   - **Goal**: the operator's words, quoted.\n   - **Scope**: one `- in:` line and one `- out:` line.\n   - **Decisions**: grill the operator with the `whetstone:grill` method: decision blocks, the recommendation first, a later round for an answer that adds or removes questions, and a fresh ask when an answer changes a premise. Look up each fact with a `gatherer` agent. Write one numbered line per decision, `\u003Cquestion> — \u003Canswer> · \u003Cdate>`.\n     - \"Discuss more\" on a decision: answer it `split into \u003Cn>, \u003Cm>` and ask the parts as new numbered decisions.\n     - A decision only someone outside the room can answer: write the `whetstone:grill` questionnaire to `questionnaire-\u003Cn>.md` in the dossier folder (`ds path`), answer the decision `waits on \u003Cwho>: \u003Cquestionnaire path>`, and add a row for it with `ds add \"\u003Ctitle>\" --who H --state wait`.\n     - Then add `confirmed: \"\u003Cthe operator's words>\"`.\n   - **Rows**: add each with `ds add \"\u003Ctitle>\"`, never by hand, before any section names it. Put row detail under `## Notes` as `### O\u003CN>`.\n   - **Checks**: each check is a command that fails today and passes when the work is done. A guard check passes today and must stay green.\n   - **Edge cases**: `- \u003Ccase> → \u003Crow or check>`.\n   - **Commits**: the planned commits, with subject, rows and paths. Plan few commits, and keep each one whole.\n2. Run `ds lint` until it prints `LINT: OK`.\n3. Run `ds check --baseline` until it prints `BASELINE: OK`.\n4. Run `ds pack plan`. In one message, spawn one `plan-checker` agent with the pack path, and, on the first check only, the subtraction pass: `whetstone:whetstone-doubter` with the subtraction mission of `whetstone:doubt-pass`, the pack as the artifact, Goal and Scope as the contract, and `model` set to this session's model family. The plan checker writes a findings file that ends `VERDICT: PASS` or `VERDICT: CHANGES`.\n5. Run `ds record plan \u003Cfindings>`.\n   - Exit 0: the plan check passed.\n   - Exit 1: change the plan for each finding, then repeat steps 2 to 5.\n   - Exit 3: this was the second CHANGES. Show the findings to the operator and stop.\n6. The subtraction pass: show its cuts to the operator in one decision block, and take only the cuts the operator picks. Then `ds log \"subtract: \u003Cits first line>; took \u003Ccut numbers or none>\"`; without Whetstone, `ds log \"subtract: skipped, no Whetstone\"`. Until that line is in the worklog, `ds handoff` asks for the cuts. A taken cut changes the plan, so repeat steps 2 to 5 without the subtraction pass.\n\nEnd the turn with the lines `ds handoff` prints.\n\nDiscovery is the long part of the work. Leave no guess in the plan: a surprise that a review finds later is a gap in this step.\n",{"name":5,"description":7,"argument-hint":24},"\u003Cslug> [goal sentence]","main","4899bb8477c28b8e2570c0a95abea3b00b33d196","plugins\u002Fdossier\u002Fskills\u002Fplan",0,"https:\u002F\u002Fgithub.com\u002Fraisedadead\u002Fclaude-code-plugins","https:\u002F\u002Fgithub.com\u002Fraisedadead","https:\u002F\u002Fmrugesh.dev","dad • dev\u002F\u002Fops • open-source","2026-11-15 01:50:10",{"source":8,"skillName":5,"commands":35,"prompt":45,"zipAvailable":46},[36,39,42],{"tool":37,"command":38},"npx","npx skills add raisedadead\u002Fclaude-code-plugins --skill plan",{"tool":40,"command":41},"bunx","bunx skills add raisedadead\u002Fclaude-code-plugins --skill plan",{"tool":43,"command":44},"pnpm","pnpm dlx skills add raisedadead\u002Fclaude-code-plugins --skill plan","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fraisedadead\u002Fclaude-code-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fdossier\u002Fskills\u002Fplan\u002FSKILL.md",true,[],[49,56,64,72,79,86],{"skillNo":50,"name":51,"nameZh":6,"description":52,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":53,"categories":54,"keywords":55,"publishedAt":19},"01M7DX0HNM8XP58PP7E4XB8E98","ship","Review the dossier branch once, fold the fixup commits into the planned commits, hand the push and PR to the operator, then watch CI. Invoke when the user says \"ds:ship\", \"ship the dossier\", or when ds next exits 4.","https:\u002F\u002Fgithub.com\u002Fraisedadead\u002Fclaude-code-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fdossier\u002Fskills\u002Fship\u002FSKILL.md",[],[],{"skillNo":57,"name":58,"nameZh":6,"description":59,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":60,"categories":61,"keywords":62,"publishedAt":63},"01M76ACYEV4AABQFW2E5F0JGDK","suite-review","Run the monthly evidence review of this repo's plugin skills. Count each skill's opportunities and uses with the census, read what happened where a skill was not used, put each skill in one bucket, act, and write the actions as predictions with a check date. Use when the operator says \"suite review\" or \"monthly review\", or when the suite-review line on LATER.md is due.","https:\u002F\u002Fgithub.com\u002Fraisedadead\u002Fclaude-code-plugins\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fsuite-review\u002FSKILL.md",[],[],"2026-11-12 13:55:43",{"skillNo":65,"name":66,"nameZh":6,"description":67,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":68,"categories":69,"keywords":70,"publishedAt":71},"01M72WDR8CPVYH4A5NS4HGD3ZT","research-report","Research a technical question with probes on the local system, a web fan-out through deep-research, a grounding pass on every load-bearing claim, and a report rendered as one HTML page. Use when the user asks for a research report, a design study or an evidence-backed recommendation about their own system.","https:\u002F\u002Fgithub.com\u002Fraisedadead\u002Fclaude-code-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fwhetstone\u002Fskills\u002Fresearch-report\u002FSKILL.md",[],[],"2026-11-10 22:39:42",{"skillNo":73,"name":74,"nameZh":6,"description":75,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":76,"categories":77,"keywords":78,"publishedAt":71},"01M72WDH4ZX9QEMCPY2KSFHDDR","html-report","Render a markdown report as one self-contained HTML page for a human reader, in plain English, with the answer first, a table of contents and Mermaid diagrams drawn as images. Use when the user asks for an HTML report, or for a readable page made from a markdown document.","https:\u002F\u002Fgithub.com\u002Fraisedadead\u002Fclaude-code-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fwhetstone\u002Fskills\u002Fhtml-report\u002FSKILL.md",[],[],{"skillNo":80,"name":81,"nameZh":6,"description":82,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":83,"categories":84,"keywords":85,"publishedAt":71},"01M72WD53HERXZ6HTZGN27SWD5","domain-modeling","Build and sharpen a project's domain model. Use when discussing codebase terminology, writing or editing a GLOSSARY.md, or recording or editing an ADR.","https:\u002F\u002Fgithub.com\u002Fraisedadead\u002Fclaude-code-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fwhetstone\u002Fskills\u002Fdomain-modeling\u002FSKILL.md",[],[],{"skillNo":87,"name":88,"nameZh":6,"description":89,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":90,"categories":91,"keywords":92,"publishedAt":71},"01M72WD0D1DKJ4A7G59Z7SY9QG","codebase-design","Shared vocabulary for designing deep modules. Use when the user wants to design or improve a module's interface, find deepening opportunities, decide where a seam goes, make code more testable or AI-navigable, or when another skill needs the deep-module vocabulary.","https:\u002F\u002Fgithub.com\u002Fraisedadead\u002Fclaude-code-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fwhetstone\u002Fskills\u002Fcodebase-design\u002FSKILL.md",[],[]]