[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7BH7CERNNFM9XH0DFRFRMPX":3,"skill-same:01M7BH7CERNNFM9XH0DFRFRMPX":46},{"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":24,"commitSha":25,"skillDirectory":26,"forksCount":27,"repositoryHtmlUrl":28,"repositoryHomepageUrl":6,"ownerHtmlUrl":29,"ownerBlogUrl":6,"ownerDescription":30,"updatedAt":31,"install":32,"resources":45},"01M7BH7CERNNFM9XH0DFRFRMPX","write-plan",null,"Write a local checklist under .tmp\u002Fgrunt\u002Fplans\u002F. Then \u002Fimplement-plan {n}.","lovrozagar\u002Fgrunt","lovrozagar","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F86857639?v=4","01M7B3T6X88HRBYP2A9ZEGQEMD","Lovro Zagar","01M7BGVF4JZBK92D0TSM09M44Q",2,"MIT","https:\u002F\u002Fgithub.com\u002Flovrozagar\u002Fgrunt\u002Fblob\u002Fmain\u002F.grok\u002Fskills\u002Fwrite-plan\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: write-plan\ndescription: 'Write a local checklist under .tmp\u002Fgrunt\u002Fplans\u002F. Then \u002Fimplement-plan {n}.'\n---\n# write-plan\n\nYou author the plan. Persist under `.tmp\u002Fgrunt\u002Fplans\u002F` via Write (hook runs `.rulesync\u002Fscripts\u002Fpersist-plan.mjs`). Format: `.rulesync\u002Freference\u002Fplan-format.md`.\n\nEmpty task → ask for a task and stop.\n\nBody starts with `PLAN_NAME: \u003C3-6 word name>`, then Goal, Usage, Context, Constraints, Watch-outs, Steps, Verify, and `## Previous mistakes` with `(none)`. Usage shows what a person or agent types and sees once the plan lands: every new or changed command, flag, output, error message, or file, in fenced blocks, with the before for each changed one; a plan with no visible change writes `No visible change:` and why. All boxes `[ ]`. Tests: new behavior or bug → failing test leaf before impl; other behavior → test leaf right after impl; docs\u002Frename\u002Fconfig\u002Fgenerated → skip. Verify is the end gate.\n\nAfter research, pick one type from `.rulesync\u002Freference\u002Fscope.md` ## Types. Context starts with `Task type: {name}` and `Named checks:`. Copy that row's checks into Steps or Verify, including a Read leaf for each named principle. Also copy a Read leaf for every fact in ## Facts that is true of this plan. No fact, no leaf. Verify includes a Read leaf for `principle-prove-it-works`. For `cross-cut`, Context also holds architect lite: types, signatures, module map, and the rejected shape. A named check that does not apply is a Context skip with a reason.\n\nBefore you ask the user, read `principle-never-block-on-the-human`. Ask only when the user alone can answer or the action is destructive. Before a large dump or a fan-out, read `principle-guard-the-context-window` and route the bulk through `node .rulesync\u002Fscripts\u002Fgrunt-job.mjs`.\n\nBefore writing, run `node .rulesync\u002Fscripts\u002Flessons.mjs match` on the absolute paths the plan names. Cite each matched lesson path in Watch-outs with what this plan does about it; the save denies a plan that leaves one out. Lessons: `.rulesync\u002Freference\u002Flessons.md`.\n\nAuthor `commit: type(scope): subject` on its own line before persist (scope optional). Conventional Commits subject: imperative lowercase, no trailing period. Types: feat fix docs style refactor perf test build ci chore revert.\n\nThe plan is the proposal and caps the result (`.rulesync\u002Freference\u002Fscope.md`). Before writing, research until every leaf is defensible; ask any plan-shaping question the user alone can answer, then research again on the answer. Do not default a plan-shaping choice. A minor open choice goes under Constraints as the chosen default plus \"confirm\".\n\nAfter the save, spawn a fresh host agent whose prompt is only `\u002Freview-plan {n}` and the plan's absolute path (on Claude Code the `claude` agent type; grunt is not the reviewer). Accept or reject each finding with a reason. Apply accepted ones to the same plan file and add one `- review: …` entry each to `## Previous mistakes`. One review round per write or revision. Bump frontmatter `reviews` by one in the same save that settles the round, even when it had no findings; send the full frontmatter for that save. Every Write that sends full frontmatter carries the current `reviews`: the save denies one that lowers or drops it.\n\nOn feedback, revise the same file (a Write of the saved path updates it in place) and add a `- feedback: …` entry for what the user rejected and what changed. Never edit or drop an earlier entry. When the mistake will happen again on other tasks, run `lessons.mjs match` on the files involved, then `lessons.mjs hit \u003Cslug> --evidence \"plan {n}\"` or write a new lesson, and end the entry with `(lesson: {slug})`.\n\nReport: serial N at the absolute path the Write returned (`\u002F…\u002F.tmp\u002Fgrunt\u002Fplans\u002F{file}`, never repo-relative), the goal, the phase list, the top risks, and any assumption to confirm. Do not dump the plan. Stop and end the reply with exactly one line, `Reply \"y\" to run plan {n}.`, or, when other reviewed plans or roadmaps from this session wait too, `Reply \"y\" to run plan {n}, then plan {m}, then roadmap {k}.` in run order. Ask for approval no other way. A bare `y` approves exactly that line. On feedback, revise this file, run `\u002Freview-plan` again, and stop again with the same line. Run `\u002Fimplement-plan {n}` in the same turn when the request said \"plan and do it\", or when `\u002Fimplement-roadmap` is running a `locked` or `in-progress` roadmap. A plan-shaping question still stops.\n","# write-plan\n\nYou author the plan. Persist under `.tmp\u002Fgrunt\u002Fplans\u002F` via Write (hook runs `.rulesync\u002Fscripts\u002Fpersist-plan.mjs`). Format: `.rulesync\u002Freference\u002Fplan-format.md`.\n\nEmpty task → ask for a task and stop.\n\nBody starts with `PLAN_NAME: \u003C3-6 word name>`, then Goal, Usage, Context, Constraints, Watch-outs, Steps, Verify, and `## Previous mistakes` with `(none)`. Usage shows what a person or agent types and sees once the plan lands: every new or changed command, flag, output, error message, or file, in fenced blocks, with the before for each changed one; a plan with no visible change writes `No visible change:` and why. All boxes `[ ]`. Tests: new behavior or bug → failing test leaf before impl; other behavior → test leaf right after impl; docs\u002Frename\u002Fconfig\u002Fgenerated → skip. Verify is the end gate.\n\nAfter research, pick one type from `.rulesync\u002Freference\u002Fscope.md` ## Types. Context starts with `Task type: {name}` and `Named checks:`. Copy that row's checks into Steps or Verify, including a Read leaf for each named principle. Also copy a Read leaf for every fact in ## Facts that is true of this plan. No fact, no leaf. Verify includes a Read leaf for `principle-prove-it-works`. For `cross-cut`, Context also holds architect lite: types, signatures, module map, and the rejected shape. A named check that does not apply is a Context skip with a reason.\n\nBefore you ask the user, read `principle-never-block-on-the-human`. Ask only when the user alone can answer or the action is destructive. Before a large dump or a fan-out, read `principle-guard-the-context-window` and route the bulk through `node .rulesync\u002Fscripts\u002Fgrunt-job.mjs`.\n\nBefore writing, run `node .rulesync\u002Fscripts\u002Flessons.mjs match` on the absolute paths the plan names. Cite each matched lesson path in Watch-outs with what this plan does about it; the save denies a plan that leaves one out. Lessons: `.rulesync\u002Freference\u002Flessons.md`.\n\nAuthor `commit: type(scope): subject` on its own line before persist (scope optional). Conventional Commits subject: imperative lowercase, no trailing period. Types: feat fix docs style refactor perf test build ci chore revert.\n\nThe plan is the proposal and caps the result (`.rulesync\u002Freference\u002Fscope.md`). Before writing, research until every leaf is defensible; ask any plan-shaping question the user alone can answer, then research again on the answer. Do not default a plan-shaping choice. A minor open choice goes under Constraints as the chosen default plus \"confirm\".\n\nAfter the save, spawn a fresh host agent whose prompt is only `\u002Freview-plan {n}` and the plan's absolute path (on Claude Code the `claude` agent type; grunt is not the reviewer). Accept or reject each finding with a reason. Apply accepted ones to the same plan file and add one `- review: …` entry each to `## Previous mistakes`. One review round per write or revision. Bump frontmatter `reviews` by one in the same save that settles the round, even when it had no findings; send the full frontmatter for that save. Every Write that sends full frontmatter carries the current `reviews`: the save denies one that lowers or drops it.\n\nOn feedback, revise the same file (a Write of the saved path updates it in place) and add a `- feedback: …` entry for what the user rejected and what changed. Never edit or drop an earlier entry. When the mistake will happen again on other tasks, run `lessons.mjs match` on the files involved, then `lessons.mjs hit \u003Cslug> --evidence \"plan {n}\"` or write a new lesson, and end the entry with `(lesson: {slug})`.\n\nReport: serial N at the absolute path the Write returned (`\u002F…\u002F.tmp\u002Fgrunt\u002Fplans\u002F{file}`, never repo-relative), the goal, the phase list, the top risks, and any assumption to confirm. Do not dump the plan. Stop and end the reply with exactly one line, `Reply \"y\" to run plan {n}.`, or, when other reviewed plans or roadmaps from this session wait too, `Reply \"y\" to run plan {n}, then plan {m}, then roadmap {k}.` in run order. Ask for approval no other way. A bare `y` approves exactly that line. On feedback, revise this file, run `\u002Freview-plan` again, and stop again with the same line. Run `\u002Fimplement-plan {n}` in the same turn when the request said \"plan and do it\", or when `\u002Fimplement-roadmap` is running a `locked` or `in-progress` roadmap. A plan-shaping question still stops.\n",{"name":5,"description":7},"main","91069c1955cc11def04b75dc2d3c4a99c9d5eb48",".grok\u002Fskills\u002Fwrite-plan",0,"https:\u002F\u002Fgithub.com\u002Flovrozagar\u002Fgrunt","https:\u002F\u002Fgithub.com\u002Flovrozagar","TypeScript Jedi Master ⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀ @workerstack ⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀ OSS & SaaS","2026-11-04 09:19:39",{"source":8,"skillName":5,"commands":33,"prompt":43,"zipAvailable":44},[34,37,40],{"tool":35,"command":36},"npx","npx skills add lovrozagar\u002Fgrunt --skill write-plan",{"tool":38,"command":39},"bunx","bunx skills add lovrozagar\u002Fgrunt --skill write-plan",{"tool":41,"command":42},"pnpm","pnpm dlx skills add lovrozagar\u002Fgrunt --skill write-plan","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Flovrozagar\u002Fgrunt\u002Fblob\u002Fmain\u002F.grok\u002Fskills\u002Fwrite-plan\u002FSKILL.md",true,[],[47,54,59,66,73,80],{"skillNo":48,"name":49,"nameZh":6,"description":50,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":51,"categories":52,"keywords":53,"publishedAt":19},"01M7BHARD0SQTQ83H73E779A8E","write-roadmap","Write an ordered program of plans under .tmp\u002Fgrunt\u002Froadmaps\u002F. Use for \u002Fwrite-roadmap. Stops for y, which locks and runs it.","https:\u002F\u002Fgithub.com\u002Flovrozagar\u002Fgrunt\u002Fblob\u002Fmain\u002F.rulesync\u002Fskills\u002Fwrite-roadmap\u002FSKILL.md",[],[],{"skillNo":55,"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":56,"categories":57,"keywords":58,"publishedAt":19},"01M7BHAQ7M9Y790C7DW0RAKAQM","https:\u002F\u002Fgithub.com\u002Flovrozagar\u002Fgrunt\u002Fblob\u002Fmain\u002F.rulesync\u002Fskills\u002Fwrite-plan\u002FSKILL.md",[],[],{"skillNo":60,"name":61,"nameZh":6,"description":62,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":63,"categories":64,"keywords":65,"publishedAt":19},"01M7BHANM3QZF2QP8P28WW9R3K","unslop","Cut AI tells from any writing. Use for \u002Funslop.","https:\u002F\u002Fgithub.com\u002Flovrozagar\u002Fgrunt\u002Fblob\u002Fmain\u002F.rulesync\u002Fskills\u002Funslop\u002FSKILL.md",[],[],{"skillNo":67,"name":68,"nameZh":6,"description":69,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":70,"categories":71,"keywords":72,"publishedAt":19},"01M7BHAM1MSNX381EDKA5HN9XM","typescript-best-practices","TypeScript best practices. Use when reading or editing any .ts or .tsx file, or for \u002Ftypescript-best-practices.","https:\u002F\u002Fgithub.com\u002Flovrozagar\u002Fgrunt\u002Fblob\u002Fmain\u002F.rulesync\u002Fskills\u002Ftypescript-best-practices\u002FSKILL.md",[],[],{"skillNo":74,"name":75,"nameZh":6,"description":76,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":77,"categories":78,"keywords":79,"publishedAt":19},"01M7BHAJX7MG58JBGEAR0NCSXW","tmp","Dump a one-off convo artifact under .tmp\u002Fgrunt\u002F.","https:\u002F\u002Fgithub.com\u002Flovrozagar\u002Fgrunt\u002Fblob\u002Fmain\u002F.rulesync\u002Fskills\u002Ftmp\u002FSKILL.md",[],[],{"skillNo":81,"name":82,"nameZh":6,"description":83,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":84,"categories":85,"keywords":86,"publishedAt":19},"01M7BHAGFXSTF5E1DDSYEZF8ZD","teach","Explain a body of work plainly so a person actually understands it. Dig into how it works and why it is that way, then weave that into one clear explanation. Use for \u002Fteach, 'teach me this', 'help me really understand X', 'explain this change or subsystem to me'.","https:\u002F\u002Fgithub.com\u002Flovrozagar\u002Fgrunt\u002Fblob\u002Fmain\u002F.rulesync\u002Fskills\u002Fteach\u002FSKILL.md",[],[]]