[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7E753S59MGMTETTJT175HZX":3,"skill-same:01M7E753S59MGMTETTJT175HZX":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":25,"commitSha":26,"skillDirectory":27,"forksCount":14,"repositoryHtmlUrl":28,"repositoryHomepageUrl":6,"ownerHtmlUrl":29,"ownerBlogUrl":30,"ownerDescription":31,"updatedAt":32,"install":33,"resources":45},"01M7E753S59MGMTETTJT175HZX","principle-sequence-verifiable-units",null,"Apply to multi-step work (sweeps, migrations, runs of similar edits) and to how you stack commits and PRs. Break work into small units that each end in a verifiable state, check each before the next, and order delivery so the sequence proves itself to a reviewer.","YunosukeYoshino\u002Fpstack-devin","YunosukeYoshino","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F26004836?v=4","01M6KMF4SG2J509712G20SECG6","YOSHINO","01M7E71V5R99WHS6SVEF43F0YB",0,"MIT","https:\u002F\u002Fgithub.com\u002FYunosukeYoshino\u002Fpstack-devin\u002Fblob\u002Fmain\u002Flib\u002Fprinciple-sequence-verifiable-units\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: principle-sequence-verifiable-units\ndescription: \"Apply to multi-step work (sweeps, migrations, runs of similar edits) and to how you stack commits and PRs. Break work into small units that each end in a verifiable state, check each before the next, and order delivery so the sequence proves itself to a reviewer.\"\ndisable-model-invocation: true\n---\n\n# Sequence work into verifiable units\n\nOrder work as a sequence of small units, each ending in a state you can check, and don't advance until the current one is green.\n\n**Why:** A break caught at the unit that caused it is cheap to localize. A break caught after a batch is buried, and you have already built further on a broken base. Sequencing those same units into a delivery a reviewer can replay turns \"trust me\" into \"watch it go red, then green.\"\n\n**Execution.** In a sweep, migration, or any run of similar edits, verify each change before starting the next. Each unit is a before\u002Fafter bracket: known-good state, one change, run the check, then proceed. Rebase onto clean trunk first so every check measures against the real baseline. When a lever does the edits, the per-unit check is nearly free. Run it anyway.\n\n**Delivery.** Stack commits and PRs in the order that proves the work. The canonical shape is the failing test first, then the fix on top. Other story orders are a subtraction before the reshape, a baseline capture before the treatment, the scaffold before the feature. Each commit lands on its own and the sequence reads as an argument.\n\n**Pattern:**\n- Pick the smallest unit that ends in a check: an edit plus its test, or a commit that stands alone.\n- Verify before advancing. Red to green per unit, never deferred to a final batch.\n- Order the units so the sequence builds confidence on its own, for you while executing and for a reviewer reading the stack.\n\nThe sequencing complement to the **prove-it-works** principle skill, which keeps each check real, and the **build-the-lever** principle skill, which makes the per-unit check cheap.\n","# Sequence work into verifiable units\n\nOrder work as a sequence of small units, each ending in a state you can check, and don't advance until the current one is green.\n\n**Why:** A break caught at the unit that caused it is cheap to localize. A break caught after a batch is buried, and you have already built further on a broken base. Sequencing those same units into a delivery a reviewer can replay turns \"trust me\" into \"watch it go red, then green.\"\n\n**Execution.** In a sweep, migration, or any run of similar edits, verify each change before starting the next. Each unit is a before\u002Fafter bracket: known-good state, one change, run the check, then proceed. Rebase onto clean trunk first so every check measures against the real baseline. When a lever does the edits, the per-unit check is nearly free. Run it anyway.\n\n**Delivery.** Stack commits and PRs in the order that proves the work. The canonical shape is the failing test first, then the fix on top. Other story orders are a subtraction before the reshape, a baseline capture before the treatment, the scaffold before the feature. Each commit lands on its own and the sequence reads as an argument.\n\n**Pattern:**\n- Pick the smallest unit that ends in a check: an edit plus its test, or a commit that stands alone.\n- Verify before advancing. Red to green per unit, never deferred to a final batch.\n- Order the units so the sequence builds confidence on its own, for you while executing and for a reviewer reading the stack.\n\nThe sequencing complement to the **prove-it-works** principle skill, which keeps each check real, and the **build-the-lever** principle skill, which makes the per-unit check cheap.\n",{"name":5,"description":7,"disable-model-invocation":24},true,"main","981ba1d05c1c7b711015fd0b3ebba5ac3cc1ef25","lib\u002Fprinciple-sequence-verifiable-units","https:\u002F\u002Fgithub.com\u002FYunosukeYoshino\u002Fpstack-devin","https:\u002F\u002Fgithub.com\u002FYunosukeYoshino","https:\u002F\u002Fyunosukeyoshino.com\u002F","Switch2が欲しい\r\n\r\n","2026-11-01 12:57:56",{"source":8,"skillName":5,"commands":34,"prompt":44,"zipAvailable":24},[35,38,41],{"tool":36,"command":37},"npx","npx skills add YunosukeYoshino\u002Fpstack-devin --skill principle-sequence-verifiable-units",{"tool":39,"command":40},"bunx","bunx skills add YunosukeYoshino\u002Fpstack-devin --skill principle-sequence-verifiable-units",{"tool":42,"command":43},"pnpm","pnpm dlx skills add YunosukeYoshino\u002Fpstack-devin --skill principle-sequence-verifiable-units","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FYunosukeYoshino\u002Fpstack-devin\u002Fblob\u002Fmain\u002Flib\u002Fprinciple-sequence-verifiable-units\u002FSKILL.md",[],[47,54,61,68,75,82],{"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},"01M7E76PXDNP9MXPTYJ6SVCQK2","pstack","poteto-mode for Devin: deliberate, verified, concise engineering mode that routes to the bundled pstack library (how, why, architect, swarm, arena, interrogate, tdd, unslop, principles, playbooks). Invoke explicitly via @skills:pstack or when the user asks for poteto \u002F pstack mode.","https:\u002F\u002Fgithub.com\u002FYunosukeYoshino\u002Fpstack-devin\u002Fblob\u002Fmain\u002Fskills\u002Fpstack\u002FSKILL.md",[],[],{"skillNo":55,"name":56,"nameZh":6,"description":57,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":58,"categories":59,"keywords":60,"publishedAt":19},"01M7E76GW88YDE0JVYEFFG8PVQ","why","Use for 'why does X work this way', 'why we picked Y', design rationale, regressions, postmortems, or data-backed thresholds. Discovers available MCPs and queries each evidence category (source control, issue tracker, long-form docs, real-time chat, infrastructure observability, error tracking, product analytics warehouse) in parallel, then returns a cited read on decisions and tradeoffs. Use how for runtime behavior.","https:\u002F\u002Fgithub.com\u002FYunosukeYoshino\u002Fpstack-devin\u002Fblob\u002Fmain\u002Flib\u002Fwhy\u002FSKILL.md",[],[],{"skillNo":62,"name":63,"nameZh":6,"description":64,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":65,"categories":66,"keywords":67,"publishedAt":19},"01M7E76FB5DBYMRAS70P9PV1ZH","unslop","Cut AI tells from any writing. Must always apply.","https:\u002F\u002Fgithub.com\u002FYunosukeYoshino\u002Fpstack-devin\u002Fblob\u002Fmain\u002Flib\u002Funslop\u002FSKILL.md",[],[],{"skillNo":69,"name":70,"nameZh":6,"description":71,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":72,"categories":73,"keywords":74,"publishedAt":19},"01M7E76DKS5VBNG72KEBZNXQJV","typescript-best-practices","TypeScript best practices. Use when reading or editing any .ts or .tsx file.","https:\u002F\u002Fgithub.com\u002FYunosukeYoshino\u002Fpstack-devin\u002Fblob\u002Fmain\u002Flib\u002Ftypescript-best-practices\u002FSKILL.md",[],[],{"skillNo":76,"name":77,"nameZh":6,"description":78,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":79,"categories":80,"keywords":81,"publishedAt":19},"01M7E769BM5JKZPH3QSCHE3HNZ","technical-writing","Layered technical-writing standard: Diátaxis structure, Google developer style sentences, STE instruction rules, Global English syntax. Use for \u002Ftechnical-writing or when writing or reviewing docs, RFCs, readmes, PR descriptions, or commit messages.","https:\u002F\u002Fgithub.com\u002FYunosukeYoshino\u002Fpstack-devin\u002Fblob\u002Fmain\u002Flib\u002Ftechnical-writing\u002FSKILL.md",[],[],{"skillNo":83,"name":84,"nameZh":6,"description":85,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":86,"categories":87,"keywords":88,"publishedAt":19},"01M7E765Y4K0CB17J2S7QZ4F59","teach","Explain a body of work plainly so a person actually understands it. Runs the `how` and `why` skills and weaves what they find into one clear explanation. Use for 'teach me this', 'help me really understand X', 'explain this change or subsystem to me'.","https:\u002F\u002Fgithub.com\u002FYunosukeYoshino\u002Fpstack-devin\u002Fblob\u002Fmain\u002Flib\u002Fteach\u002FSKILL.md",[],[]]