[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7F0HF65K3KB889MSVCHB8B5":3,"skill-same:01M7F0HF65K3KB889MSVCHB8B5":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":25,"commitSha":26,"skillDirectory":27,"forksCount":14,"repositoryHtmlUrl":28,"repositoryHomepageUrl":6,"ownerHtmlUrl":29,"ownerBlogUrl":30,"ownerDescription":6,"updatedAt":31,"install":32,"resources":44},"01M7F0HF65K3KB889MSVCHB8B5","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.","irfanalimd\u002Fpstack-ports","irfanalimd","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F55896554?v=4","01M7F0CXJRB2KHNDXGYJDG9R65","Mohammed Irfan Ali","01M7F0CXKNYHJDNQ8RREHX0ZG0",0,"MIT","https:\u002F\u002Fgithub.com\u002Firfanalimd\u002Fpstack-ports\u002Fblob\u002Fmain\u002Fclaude-code\u002Fpstack\u002Fskills\u002Fprinciple-sequence-verifiable-units\u002FSKILL.md",[],[],"2026-11-16 10:05:34",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\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\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","3cf90aeb365f524d07ef38f0fb3cbad19aeecc6f","claude-code\u002Fpstack\u002Fskills\u002Fprinciple-sequence-verifiable-units","https:\u002F\u002Fgithub.com\u002Firfanalimd\u002Fpstack-ports","https:\u002F\u002Fgithub.com\u002Firfanalimd","irfanali.me","2026-10-17 07:04:24",{"source":8,"skillName":5,"commands":33,"prompt":43,"zipAvailable":24},[34,37,40],{"tool":35,"command":36},"npx","npx skills add irfanalimd\u002Fpstack-ports --skill principle-sequence-verifiable-units",{"tool":38,"command":39},"bunx","bunx skills add irfanalimd\u002Fpstack-ports --skill principle-sequence-verifiable-units",{"tool":41,"command":42},"pnpm","pnpm dlx skills add irfanalimd\u002Fpstack-ports --skill principle-sequence-verifiable-units","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Firfanalimd\u002Fpstack-ports\u002Fblob\u002Fmain\u002Fclaude-code\u002Fpstack\u002Fskills\u002Fprinciple-sequence-verifiable-units\u002FSKILL.md",[],[46,53,60,67,74,81],{"skillNo":47,"name":48,"nameZh":6,"description":49,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":50,"categories":51,"keywords":52,"publishedAt":19},"01M7F0ZB3XY54V5W1VACEVX58W","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\u002Firfanalimd\u002Fpstack-ports\u002Fblob\u002Fmain\u002Fupstream\u002Fpstack\u002Fskills\u002Fwhy\u002FSKILL.md",[],[],{"skillNo":54,"name":55,"nameZh":6,"description":56,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":57,"categories":58,"keywords":59,"publishedAt":19},"01M7F0Z9GHCK4T0WPSBEBAEMB7","unslop","Cut AI tells from any writing.","https:\u002F\u002Fgithub.com\u002Firfanalimd\u002Fpstack-ports\u002Fblob\u002Fmain\u002Fupstream\u002Fpstack\u002Fskills\u002Funslop\u002FSKILL.md",[],[],{"skillNo":61,"name":62,"nameZh":6,"description":63,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":64,"categories":65,"keywords":66,"publishedAt":19},"01M7F0Z7K4GWX9DDDD13G98GBE","typescript-best-practices","TypeScript best practices. Use when reading or editing any .ts or .tsx file.","https:\u002F\u002Fgithub.com\u002Firfanalimd\u002Fpstack-ports\u002Fblob\u002Fmain\u002Fupstream\u002Fpstack\u002Fskills\u002Ftypescript-best-practices\u002FSKILL.md",[],[],{"skillNo":68,"name":69,"nameZh":6,"description":70,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":71,"categories":72,"keywords":73,"publishedAt":19},"01M7F0Z3ATKTCM4ZEFP0V8YW90","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\u002Firfanalimd\u002Fpstack-ports\u002Fblob\u002Fmain\u002Fupstream\u002Fpstack\u002Fskills\u002Ftechnical-writing\u002FSKILL.md",[],[],{"skillNo":75,"name":76,"nameZh":6,"description":77,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":78,"categories":79,"keywords":80,"publishedAt":19},"01M7F0YZW6SA7BJN6WA9T58GGX","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\u002Firfanalimd\u002Fpstack-ports\u002Fblob\u002Fmain\u002Fupstream\u002Fpstack\u002Fskills\u002Fteach\u002FSKILL.md",[],[],{"skillNo":82,"name":83,"nameZh":6,"description":84,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":85,"categories":86,"keywords":87,"publishedAt":19},"01M7F0YWN310MAHQWZF0ADYADS","tdd","Use only when the user explicitly asks for TDD, a failing test, or a regression test, OR when the bug has an obvious cheap local test target. Skip when the test path is unclear, expensive, integration-heavy, or not requested.","https:\u002F\u002Fgithub.com\u002Firfanalimd\u002Fpstack-ports\u002Fblob\u002Fmain\u002Fupstream\u002Fpstack\u002Fskills\u002Ftdd\u002FSKILL.md",[],[]]