[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7F3YA065DD0VAV3CPF7BWAY":3,"skill-same:01M7F3YA065DD0VAV3CPF7BWAY":45},{"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":14,"repositoryHtmlUrl":27,"repositoryHomepageUrl":6,"ownerHtmlUrl":28,"ownerBlogUrl":29,"ownerDescription":6,"updatedAt":30,"install":31,"resources":44},"01M7F3YA065DD0VAV3CPF7BWAY","plan",null,"Write the plan file in docs\u002Fplans\u002F that code changes get before building, unless the user has said to build without one. Use when the user asks to build, fix, edit or change code and docs\u002Fplans\u002F has no approved plan for it, or when a plan must be revised after review. Plan step of the methodical loop. Not for questions or reading code, and not when the user has waived the plan for this change (go to work).","BigLeverVentures\u002Fmethodical-gated-engineering","BigLeverVentures","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F196365016?v=4","01M7F3V567G0YQ3QWY39AHD9BN","Big Lever Ventures","01M7F3V56S1VHYERWFCQM018V7",0,"MIT","https:\u002F\u002Fgithub.com\u002FBigLeverVentures\u002Fmethodical-gated-engineering\u002Fblob\u002Fmain\u002Fplugins\u002Fmethodical-codex\u002Fskills\u002Fplan\u002FSKILL.md",[],[],"2026-11-16 10:05:34",false,"---\nname: plan\ndescription: \"Write the plan file in docs\u002Fplans\u002F that code changes get before building, unless the user has said to build without one. Use when the user asks to build, fix, edit or change code and docs\u002Fplans\u002F has no approved plan for it, or when a plan must be revised after review. Plan step of the methodical loop. Not for questions or reading code, and not when the user has waived the plan for this change (go to work).\"\n---\n\n# Plan\n\nSay `Step: plan` before anything else.\n\n## What it produces\n\n`docs\u002Fplans\u002F\u003CYYYY-MM-DD>-\u003Cslug>.md`, made from `${PLUGIN_ROOT}\u002Ftemplates\u002Fplan.md`, with every\nsection filled or explicitly marked \"none\".\n\nThe plan's `base:` is the commit it was written against. Why: a reviewer can only check a plan\nagainst the code it was written for, and a stale base is itself a reason to deepen.\n\nThe plan is a deciding seat, written on the decider's row, which stays the decider's row at every\nescalation level. If this session runs on another model, launch a `general-purpose` Agent with the\ndecider's model and effort to draft it, and give that seat the base commit and the brainstorm. If that launch fails, follow the re-seat ladder in\n`${PLUGIN_ROOT}\u002Freference\u002Fseat-selection.md`.\n\n## How\n\n1. **Take the inventory from the code, not from memory.** Every file, module, interface and\n   document the unit touches, with what changes.\n2. **Look for prior art** in `docs\u002Fsolutions\u002F` and name what applies.\n3. **Score deepen against the always-on rules' triggers**, fill the Deepen score section, and say\n   the score aloud (\"Deepen score: 3 of 6, deepening; escalation: lean\"). Below 2, run it anyway\n   if it would help, and say why. Why: saying the score lets the user overrule it.\n\n   **Set the escalation level.** This step computes the line once and writes it as `escalation:` in\n   the front matter: `full` at a score of 4 or more, `lean` at 3 or at a named trigger\n   (Escalation in `${PLUGIN_ROOT}\u002Freference\u002Fseat-selection.md`), otherwise `none`. The\n   Deepen score section records which trigger set the level, with its evidence. If the user edits\n   the line before approving, the user's edit stands and is recorded as a ruling; a deepen or\n   review revision recomputes only when no such edit is recorded. Work reads the approved plan's\n   line. Why: the level is decided where the risk is known, and the user's edit outranks the\n   computation.\n4. **Write acceptance tests the person served would recognise**, each with how it is run and what\n   counts as a pass.\n5. **Record rulings** in the Rulings section as they are given, after you read\n   `${PLUGIN_ROOT}\u002Frules\u002Fuser-words.md` and follow it.\n6. **Commit the plan.** If the repo is on `main`, first create the unit's branch (see the work\n   skill), so the plan and its work merge together.\n\n## When it hands on\n\n- Score 2 or more, or a stale base: say `Step: deepen` and continue with the deepen skill in the same turn.\n- Otherwise: say `Step: plan-review` and run `\u002Fmethodical:plan-review` in the same turn.\n\nLeave the plan at `state: draft`. Plan review sets `reviewed`. The question\n\"Approve this plan?\" comes next: plan-review asks it with the native structured-question tool, as its own final call\nafter the open-question answers are in the plan; record their answer in Rulings, and set `state: approved` only on their yes. Why: the user,\nnot a reviewer, rules that a plan gets built; that stop is what makes the method gated. Open\nquestions wait for their ruling while everything that does not depend on them continues.\n","# Plan\n\nSay `Step: plan` before anything else.\n\n## What it produces\n\n`docs\u002Fplans\u002F\u003CYYYY-MM-DD>-\u003Cslug>.md`, made from `${PLUGIN_ROOT}\u002Ftemplates\u002Fplan.md`, with every\nsection filled or explicitly marked \"none\".\n\nThe plan's `base:` is the commit it was written against. Why: a reviewer can only check a plan\nagainst the code it was written for, and a stale base is itself a reason to deepen.\n\nThe plan is a deciding seat, written on the decider's row, which stays the decider's row at every\nescalation level. If this session runs on another model, launch a `general-purpose` Agent with the\ndecider's model and effort to draft it, and give that seat the base commit and the brainstorm. If that launch fails, follow the re-seat ladder in\n`${PLUGIN_ROOT}\u002Freference\u002Fseat-selection.md`.\n\n## How\n\n1. **Take the inventory from the code, not from memory.** Every file, module, interface and\n   document the unit touches, with what changes.\n2. **Look for prior art** in `docs\u002Fsolutions\u002F` and name what applies.\n3. **Score deepen against the always-on rules' triggers**, fill the Deepen score section, and say\n   the score aloud (\"Deepen score: 3 of 6, deepening; escalation: lean\"). Below 2, run it anyway\n   if it would help, and say why. Why: saying the score lets the user overrule it.\n\n   **Set the escalation level.** This step computes the line once and writes it as `escalation:` in\n   the front matter: `full` at a score of 4 or more, `lean` at 3 or at a named trigger\n   (Escalation in `${PLUGIN_ROOT}\u002Freference\u002Fseat-selection.md`), otherwise `none`. The\n   Deepen score section records which trigger set the level, with its evidence. If the user edits\n   the line before approving, the user's edit stands and is recorded as a ruling; a deepen or\n   review revision recomputes only when no such edit is recorded. Work reads the approved plan's\n   line. Why: the level is decided where the risk is known, and the user's edit outranks the\n   computation.\n4. **Write acceptance tests the person served would recognise**, each with how it is run and what\n   counts as a pass.\n5. **Record rulings** in the Rulings section as they are given, after you read\n   `${PLUGIN_ROOT}\u002Frules\u002Fuser-words.md` and follow it.\n6. **Commit the plan.** If the repo is on `main`, first create the unit's branch (see the work\n   skill), so the plan and its work merge together.\n\n## When it hands on\n\n- Score 2 or more, or a stale base: say `Step: deepen` and continue with the deepen skill in the same turn.\n- Otherwise: say `Step: plan-review` and run `\u002Fmethodical:plan-review` in the same turn.\n\nLeave the plan at `state: draft`. Plan review sets `reviewed`. The question\n\"Approve this plan?\" comes next: plan-review asks it with the native structured-question tool, as its own final call\nafter the open-question answers are in the plan; record their answer in Rulings, and set `state: approved` only on their yes. Why: the user,\nnot a reviewer, rules that a plan gets built; that stop is what makes the method gated. Open\nquestions wait for their ruling while everything that does not depend on them continues.\n",{"name":5,"description":7},"main","67bcf3c285965a9714d303252d8023a960a82511","plugins\u002Fmethodical-codex\u002Fskills\u002Fplan","https:\u002F\u002Fgithub.com\u002FBigLeverVentures\u002Fmethodical-gated-engineering","https:\u002F\u002Fgithub.com\u002FBigLeverVentures","www.bigleverventures.com","2026-11-15 10:50:39",{"source":8,"skillName":5,"commands":32,"prompt":42,"zipAvailable":43},[33,36,39],{"tool":34,"command":35},"npx","npx skills add BigLeverVentures\u002Fmethodical-gated-engineering --skill plan",{"tool":37,"command":38},"bunx","bunx skills add BigLeverVentures\u002Fmethodical-gated-engineering --skill plan",{"tool":40,"command":41},"pnpm","pnpm dlx skills add BigLeverVentures\u002Fmethodical-gated-engineering --skill plan","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FBigLeverVentures\u002Fmethodical-gated-engineering\u002Fblob\u002Fmain\u002Fplugins\u002Fmethodical-codex\u002Fskills\u002Fplan\u002FSKILL.md",true,[],[46,52,58,65,72,77],{"skillNo":47,"name":48,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":49,"categories":50,"keywords":51,"publishedAt":19},"01M7F3ZT8YMJ3EZ6RDQ20X5SVF","phrase-outside","https:\u002F\u002Fgithub.com\u002FBigLeverVentures\u002Fmethodical-gated-engineering\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Fhand-off\u002Fphrase-outside\u002FSKILL.md",[],[],{"skillNo":53,"name":54,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":55,"categories":56,"keywords":57,"publishedAt":19},"01M7F3ZR6P6W75DY7QVP7TP9NT","named-only","https:\u002F\u002Fgithub.com\u002FBigLeverVentures\u002Fmethodical-gated-engineering\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Fhand-off\u002Fnamed-only\u002FSKILL.md",[],[],{"skillNo":59,"name":60,"nameZh":6,"description":61,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":62,"categories":63,"keywords":64,"publishedAt":19},"01M7F3ZMHBD3K2WMEFC5XS2224","work","Build an approved plan from docs\u002Fplans\u002F on its own short-lived branch, or a change the user said to make without a plan. Use when a plan reads state: approved and the user wants it built, when resuming such a build, or when the user has waived the plan for a named change. Work step of the methodical loop. Not when no approved plan exists and the user has not waived one (run the plan step), and not for reviewing finished work.","https:\u002F\u002Fgithub.com\u002FBigLeverVentures\u002Fmethodical-gated-engineering\u002Fblob\u002Fmain\u002Fplugins\u002Fmethodical\u002Fskills\u002Fwork\u002FSKILL.md",[],[],{"skillNo":66,"name":67,"nameZh":6,"description":68,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":69,"categories":70,"keywords":71,"publishedAt":19},"01M7F3ZFVSDD9CMC6X63S8TWK5","work-review","Review a finished build on its branch against its plan, with reviewer seats matched to the code's language, before it merges. Use when the work step's tests pass and the plan's approach is done, or when the user asks for a review of a branch's changes. Work-review step of the methodical loop. Not for reviewing a plan.","https:\u002F\u002Fgithub.com\u002FBigLeverVentures\u002Fmethodical-gated-engineering\u002Fblob\u002Fmain\u002Fplugins\u002Fmethodical\u002Fskills\u002Fwork-review\u002FSKILL.md",[],[],{"skillNo":73,"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":74,"categories":75,"keywords":76,"publishedAt":19},"01M7F3ZC9EXRTW3D90JRAV32ED","https:\u002F\u002Fgithub.com\u002FBigLeverVentures\u002Fmethodical-gated-engineering\u002Fblob\u002Fmain\u002Fplugins\u002Fmethodical\u002Fskills\u002Fplan\u002FSKILL.md",[],[],{"skillNo":78,"name":79,"nameZh":6,"description":80,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":81,"categories":82,"keywords":83,"publishedAt":19},"01M7F3Z8YMRZJDESVP61JQHM27","plan-review","Review a plan in docs\u002Fplans\u002F with reviewer seats matched to the project's language, before the user approves it. Use when a plan has just been written or deepened, when a plan was revised after review, or when the user asks for a plan review. Plan-review step of the methodical loop. Not for reviewing built code.","https:\u002F\u002Fgithub.com\u002FBigLeverVentures\u002Fmethodical-gated-engineering\u002Fblob\u002Fmain\u002Fplugins\u002Fmethodical\u002Fskills\u002Fplan-review\u002FSKILL.md",[],[]]