[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7F7VYNXTZ9R9DSTG90YFJP8":3,"skill-same:01M7F7VYNXTZ9R9DSTG90YFJP8":44},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":18,"linkOnly":19,"markdownContent":20,"markdownBody":21,"frontMatter":22,"refName":23,"commitSha":24,"skillDirectory":25,"forksCount":26,"repositoryHtmlUrl":27,"repositoryHomepageUrl":6,"ownerHtmlUrl":28,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":29,"install":30,"resources":43},"01M7F7VYNXTZ9R9DSTG90YFJP8","figure-it-out",null,"Design an auditable playbook when no narrower one fits, scaling rigor to a large migration or multi-part change. Use for figure it out.","bitgineer\u002Fopencode-pstack","bitgineer","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F133060368?v=4","01M7F7V139SDYHXSH9GXXM8EV7","01M7F7V13Y1ZZCY3J922JX06QC",1,"MIT","https:\u002F\u002Fgithub.com\u002Fbitgineer\u002Fopencode-pstack\u002Fblob\u002Fmain\u002Fskills\u002Fpstack\u002Ffigure-it-out\u002FSKILL.md",[],[],"2026-11-16 10:05:34",false,"---\nname: figure-it-out\ndescription: \"Design an auditable playbook when no narrower one fits, scaling rigor to a large migration or multi-part change. Use for figure it out.\"\n\n---\n\n# Figure it out\n\nWhen the task matches no playbook, design one. The deliverable before any code is the workflow itself: a sequence of phases that scales rigor to the task, runs the scientific method, and leaves a decision trail a human can audit after stepping away.\n\n## Start\n\nOpen a todolist whose first item is to read the Principles section of the **poteto-mode** skill. Then add the phases below as todos.\n\n## Phase A: Frame\n\nGround first, then commit. Don't start the run until you can state:\n\n- The definition of done as a falsifiable predicate (the **prove-it-works** principle skill).\n- Scope, quantified: rough units and effort, plus the blockers grounding surfaced.\n- The rigor level, biased high. One-way doors and high blast radius get more. Reversible low-stakes steps get less. Rigor is gates and artifacts, not \"try harder\".\n\nPresent the framing and tradeoffs before committing to a long run. Reversible work proceeds (the **never-block-on-the-human** principle skill), but a multi-hour run earns one checkpoint.\n\n## Phase B: Design the workflow\n\nDecompose into atomic, independently-landable units. Sequence riskiest-unknown-first. Scaffold and verification come before features (the **foundational-thinking** principle skill).\n\n- Build the verification harness before the work, with the baseline captured from the pre-change state, so the check reads as \"old value vs new value\".\n- For one-way-door design decisions, run the **architect** skill (it runs **arena**). Skip it for mechanical work whose shape is already concrete. A second arena over a settled design is over-engineering (the **laziness-protocol** principle skill).\n- Decide what fans out. Parallelize only across seams, and give each worker its own worktree or branch (the **separate-before-serializing-shared-state** principle skill). Don't over-fan. Do not pass a model. Each role agent carries its own, set by `\u002Fpstack\u002Fsetup-pstack`, which writes the `model:` line of every role agent.\n- Write the designed phase list down. That list is what the human reviews.\n\nThen execute the design. Add its steps to the todolist as concrete items between the Phase C and Phase D entries. Run each under the Phase C loop discipline, and weave the Phase D log through them, a row as each step lands, rather than saving the whole trail for the end.\n\n## Phase C: Run the loop\n\nEach unit is an experiment. State the hypothesis, make the smallest change, measure against the predicate on the real artifact, keep it if it advanced, revert it if it didn't. Apply the **sequence-verifiable-units** principle skill, verifying each unit before starting the next instead of batching checks at the end.\n\n- Verify by inspecting the artifact, never a self-report. When something passes too easily, suspect the observation method before the system.\n- Pair delegated work with a judge. If a worker games the gate, reset and harden the contract. If the gate itself is wrong, fix the gate in its own change rather than routing around it.\n- A verdict is VERIFIED, NOT VERIFIED, or INCONCLUSIVE. Inconclusive is not a pass. Don't hide a negative.\n\n## Phase D: Keep the audit trail\n\nLog the run via the **show-me-your-work** skill. figure-it-out's work is usually ambitious enough to commit the trail so the reviewer can read it in the PR. The trail plus the diff is what lets the human come back and trust the work.\n\n## Phase E: Verify and hand back\n\nCheck the whole against the Phase A predicate on the real product, not just the harness. Encode any recurring correction as a gate, a lint rule, a check, or a script (the **encode-lessons-in-structure** principle skill).\n\n**Reply:** the playbook you designed, the rigor level and why, the decision-trail path, what's verified against the predicate, and what's still open.\n","# Figure it out\n\nWhen the task matches no playbook, design one. The deliverable before any code is the workflow itself: a sequence of phases that scales rigor to the task, runs the scientific method, and leaves a decision trail a human can audit after stepping away.\n\n## Start\n\nOpen a todolist whose first item is to read the Principles section of the **poteto-mode** skill. Then add the phases below as todos.\n\n## Phase A: Frame\n\nGround first, then commit. Don't start the run until you can state:\n\n- The definition of done as a falsifiable predicate (the **prove-it-works** principle skill).\n- Scope, quantified: rough units and effort, plus the blockers grounding surfaced.\n- The rigor level, biased high. One-way doors and high blast radius get more. Reversible low-stakes steps get less. Rigor is gates and artifacts, not \"try harder\".\n\nPresent the framing and tradeoffs before committing to a long run. Reversible work proceeds (the **never-block-on-the-human** principle skill), but a multi-hour run earns one checkpoint.\n\n## Phase B: Design the workflow\n\nDecompose into atomic, independently-landable units. Sequence riskiest-unknown-first. Scaffold and verification come before features (the **foundational-thinking** principle skill).\n\n- Build the verification harness before the work, with the baseline captured from the pre-change state, so the check reads as \"old value vs new value\".\n- For one-way-door design decisions, run the **architect** skill (it runs **arena**). Skip it for mechanical work whose shape is already concrete. A second arena over a settled design is over-engineering (the **laziness-protocol** principle skill).\n- Decide what fans out. Parallelize only across seams, and give each worker its own worktree or branch (the **separate-before-serializing-shared-state** principle skill). Don't over-fan. Do not pass a model. Each role agent carries its own, set by `\u002Fpstack\u002Fsetup-pstack`, which writes the `model:` line of every role agent.\n- Write the designed phase list down. That list is what the human reviews.\n\nThen execute the design. Add its steps to the todolist as concrete items between the Phase C and Phase D entries. Run each under the Phase C loop discipline, and weave the Phase D log through them, a row as each step lands, rather than saving the whole trail for the end.\n\n## Phase C: Run the loop\n\nEach unit is an experiment. State the hypothesis, make the smallest change, measure against the predicate on the real artifact, keep it if it advanced, revert it if it didn't. Apply the **sequence-verifiable-units** principle skill, verifying each unit before starting the next instead of batching checks at the end.\n\n- Verify by inspecting the artifact, never a self-report. When something passes too easily, suspect the observation method before the system.\n- Pair delegated work with a judge. If a worker games the gate, reset and harden the contract. If the gate itself is wrong, fix the gate in its own change rather than routing around it.\n- A verdict is VERIFIED, NOT VERIFIED, or INCONCLUSIVE. Inconclusive is not a pass. Don't hide a negative.\n\n## Phase D: Keep the audit trail\n\nLog the run via the **show-me-your-work** skill. figure-it-out's work is usually ambitious enough to commit the trail so the reviewer can read it in the PR. The trail plus the diff is what lets the human come back and trust the work.\n\n## Phase E: Verify and hand back\n\nCheck the whole against the Phase A predicate on the real product, not just the harness. Encode any recurring correction as a gate, a lint rule, a check, or a script (the **encode-lessons-in-structure** principle skill).\n\n**Reply:** the playbook you designed, the rigor level and why, the decision-trail path, what's verified against the predicate, and what's still open.\n",{"name":5,"description":7},"main","dbb7a4935f614ebaec65ca3beb181bf74ed53431","skills\u002Fpstack\u002Ffigure-it-out",0,"https:\u002F\u002Fgithub.com\u002Fbitgineer\u002Fopencode-pstack","https:\u002F\u002Fgithub.com\u002Fbitgineer","2026-10-21 18:58:00",{"source":8,"skillName":5,"commands":31,"prompt":41,"zipAvailable":42},[32,35,38],{"tool":33,"command":34},"npx","npx skills add bitgineer\u002Fopencode-pstack --skill figure-it-out",{"tool":36,"command":37},"bunx","bunx skills add bitgineer\u002Fopencode-pstack --skill figure-it-out",{"tool":39,"command":40},"pnpm","pnpm dlx skills add bitgineer\u002Fopencode-pstack --skill figure-it-out","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fbitgineer\u002Fopencode-pstack\u002Fblob\u002Fmain\u002Fskills\u002Fpstack\u002Ffigure-it-out\u002FSKILL.md",true,[],[45,52,59,66,73,80],{"skillNo":46,"name":47,"nameZh":6,"description":48,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":49,"categories":50,"keywords":51,"publishedAt":18},"01M7F8095YEQBD1R95S3CQNM7M","why","Trace why code works this way or why a design was chosen, from source control, trackers, docs, and telemetry. Use for rationale, regressions, or postmortems.","https:\u002F\u002Fgithub.com\u002Fbitgineer\u002Fopencode-pstack\u002Fblob\u002Fmain\u002Fskills\u002Fpstack\u002Fwhy\u002FSKILL.md",[],[],{"skillNo":53,"name":54,"nameZh":6,"description":55,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":56,"categories":57,"keywords":58,"publishedAt":18},"01M7F807MX84XR7FGZ1YTDPNPP","unslop","Cut AI tells from any writing.","https:\u002F\u002Fgithub.com\u002Fbitgineer\u002Fopencode-pstack\u002Fblob\u002Fmain\u002Fskills\u002Fpstack\u002Funslop\u002FSKILL.md",[],[],{"skillNo":60,"name":61,"nameZh":6,"description":62,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":63,"categories":64,"keywords":65,"publishedAt":18},"01M7F804Y0KW517P76ZAYQ86ED","typescript-best-practices","TypeScript best practices. Use when reading or editing any .ts or .tsx file.","https:\u002F\u002Fgithub.com\u002Fbitgineer\u002Fopencode-pstack\u002Fblob\u002Fmain\u002Fskills\u002Fpstack\u002Ftypescript-best-practices\u002FSKILL.md",[],[],{"skillNo":67,"name":68,"nameZh":6,"description":69,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":70,"categories":71,"keywords":72,"publishedAt":18},"01M7F800R1VV08YF0AKMNTPZ2J","technical-writing","Write or review docs, RFCs, readmes, PR descriptions, and commit messages in Diataxis structure with Google style, STE, and Global English.","https:\u002F\u002Fgithub.com\u002Fbitgineer\u002Fopencode-pstack\u002Fblob\u002Fmain\u002Fskills\u002Fpstack\u002Ftechnical-writing\u002FSKILL.md",[],[],{"skillNo":74,"name":75,"nameZh":6,"description":76,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":77,"categories":78,"keywords":79,"publishedAt":18},"01M7F7ZX5TJ2049PWXHB07MA7Y","teach","Explain a body of work so a person actually understands it, running how and why and weaving both into one clear explanation. Use for teach me this.","https:\u002F\u002Fgithub.com\u002Fbitgineer\u002Fopencode-pstack\u002Fblob\u002Fmain\u002Fskills\u002Fpstack\u002Fteach\u002FSKILL.md",[],[],{"skillNo":81,"name":82,"nameZh":6,"description":83,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":84,"categories":85,"keywords":86,"publishedAt":18},"01M7F7ZSN544YPV34WWVFW332X","tdd","Use only when the user asks for TDD, a failing test, or a regression test, or when a bug has a cheap local test target; skip unclear or costly test paths.","https:\u002F\u002Fgithub.com\u002Fbitgineer\u002Fopencode-pstack\u002Fblob\u002Fmain\u002Fskills\u002Fpstack\u002Ftdd\u002FSKILL.md",[],[]]