[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M79PP1X024NMATB1C2W5C911":3,"skill-same:01M79PP1X024NMATB1C2W5C911":60},{"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":27,"commitSha":28,"skillDirectory":29,"forksCount":14,"repositoryHtmlUrl":30,"repositoryHomepageUrl":6,"ownerHtmlUrl":31,"ownerBlogUrl":32,"ownerDescription":33,"updatedAt":34,"install":35,"resources":47},"01M79PP1X024NMATB1C2W5C911","implement-stack",null,"Implement a spec, issue, issue set, or free-form request as a dependency-ordered stack of reviewable pull requests.","nick-neely\u002Fagent-skills","nick-neely","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F49537823?v=4","01M79PN6YVPE30QN6V8RFVE3HX","Nick Neely","01M79PN7002TSYJ8RTQFBT3SDM",0,"MIT","https:\u002F\u002Fgithub.com\u002Fnick-neely\u002Fagent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fimplement-stack\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: implement-stack\ndescription: Implement a spec, issue, issue set, or free-form request as a dependency-ordered stack of reviewable pull requests.\ncompatibility: Requires Node.js, git, GitHub CLI with gh stack, and the gh-stack, tdd, and code-review skills.\ndisable-model-invocation: true\nargument-hint: \"\u003Cissue, spec, or direction>...\"\n---\n\n# Implement Stack\n\nImplement `$ARGUMENTS` as one or more stacked pull request stories. Apply the\nper-layer lifecycle below while this skill controls the branch and stack\nboundaries. Load the supporting model-invoked skills at their named steps:\n\n- Run $gh-stack before choosing layers, then follow it for stack design,\n  commands, recovery, synchronization, and submission.\n- Run $tdd at the pre-agreed seams during implementation.\n- Run $code-review against each branch's parent before the layer is complete.\n\nPlan the stack before editing. Build each concern on its owning branch instead of\nimplementing everything together and splitting the diff afterwards.\n\n## 1. Ground the work\n\nReplace `\u003Cskill-root>` with the directory containing this skill's `SKILL.md`,\nthen run the deterministic preflight before inspecting or changing files:\n\n```sh\nnode \"\u003Cskill-root>\u002Fscripts\u002Fpreflight.mjs\" --live --json\n```\n\nRun the command through the harness's host or escalated path when GitHub network\naccess is sandboxed. The script installs and configures nothing. A dirty worktree\nand disabled `rerere` are warnings; every failed required check blocks the run.\n\n- Read every supplied issue, spec, and direction in full. Fetch live tracker\n  state when the input names tickets.\n- Inspect the repository instructions, current branch, worktree, relevant code,\n  and available test and verification commands.\n- Preserve unrelated worktree changes. Stop only when overlap makes safe branch\n  ownership impossible or the requested behavior has material ambiguity.\n- Treat `gh stack init` as the authoritative repository-availability check when\n  preflight reports that the current branch is not yet stacked. Exit code 9\n  blocks the run before file edits.\n\nThis step is complete when every requested behavior and repository constraint is\naccounted for in the stack plan.\n\n## 2. Design the review story\n\nChoose the smallest dependency-ordered set of layers that makes each pull\nrequest understandable and useful:\n\n- Keep one coherent feature or project in a stack. Put independent work in\n  separate stacks rather than forcing a linear dependency.\n- For several issues, use one layer per issue only when issue boundaries also\n  form a clean dependency and review boundary.\n- For one large issue, split at real seams such as prerequisite refactoring,\n  domain behavior, integration, or a distinct consumer. Prefer end-to-end\n  behavior over arbitrary file or architecture layers.\n- Give every layer a one-sentence purpose. Each layer must be independently\n  reviewable, pass the checks its diff implicates, and leave its parent in a\n  coherent state.\n- Put shared foundations below their consumers. Assign each planned code change,\n  test, migration, and document to one owning layer before implementation.\n- Follow repository branch conventions. Otherwise use a shared topic prefix and\n  a specific concern suffix.\n\nProceed without a planning checkpoint unless a product choice would materially\nchange the stack or implementation.\n\n## 3. Create the stack first\n\nStart the bottom branch with `gh stack init \u003Cbranch>...` before writing code.\nImplement bottom to top. Add the next branch only after the current layer is\ncommitted and its worktree is clean.\n\nWhen continuing an existing stack, inspect it with `gh stack view --json` and\ncheck out the branch that owns a change before editing. After changing a lower\nlayer, rebase every branch above it and return to the top.\n\n## 4. Implement each layer\n\nFor each branch, apply a tight implementation loop:\n\n1. Run $tdd at the pre-agreed seams, one red-green vertical slice at a time.\n2. Typecheck and run focused tests regularly while implementing.\n3. Run every focused gate needed to show that this layer is independently green.\n4. Stage deliberately and commit the candidate layer to its current branch.\n5. Run $code-review against the parent branch. Fix every actionable finding on\n   the owning layer, rerun its gates, and commit the fixes with intentional\n   history.\n6. Confirm the layer has one review story and a clean worktree, then create the\n   next branch.\n\nTests for a layer's behavior belong in that layer. Reserve a final integration\nlayer for behavior that genuinely requires the complete stack.\n\n## 5. Verify the complete stack\n\nFrom the top branch, run the repository's full test suite once and every final\nverification lane implicated by the complete diff.\n\nAttribute a failure to its owning layer. Check out that branch, fix and commit it,\nrebase the upstack branches, return to the top, then rerun the affected checks and\nthe final verification. Inspect each branch diff against its parent so lower-layer\nwork has not leaked into a later review.\n\nThis step is complete only when every layer is reviewable on its own and the top\nof the stack passes the full verification contract.\n\n## 6. Submit the pull requests\n\nTreat invocation of this skill as authorization to push the planned stack and\ncreate its pull requests after local verification. It does not authorize merging.\n\n- Use `gh stack submit --auto` to create draft pull requests by default. Use\n  `--open` only when the user asked for ready-for-review pull requests.\n- Give each pull request a layer-scoped title and body. Include its purpose,\n  parent dependency, verification, issue links, and stack position.\n- Use `Closes #N` only on the layer that fully delivers that issue. Use a\n  non-closing issue reference on prerequisite or partial layers.\n- Confirm the final branch order, bases, pull request URLs, and states with\n  `gh stack view --json`.\n\n## Done\n\nReport the stack bottom to top with each pull request URL, its purpose, its local\nverification, and any remaining external checks. All planned layers are\ncommitted, locally green, submitted, and represented in the reported stack.\n","# Implement Stack\n\nImplement `$ARGUMENTS` as one or more stacked pull request stories. Apply the\nper-layer lifecycle below while this skill controls the branch and stack\nboundaries. Load the supporting model-invoked skills at their named steps:\n\n- Run $gh-stack before choosing layers, then follow it for stack design,\n  commands, recovery, synchronization, and submission.\n- Run $tdd at the pre-agreed seams during implementation.\n- Run $code-review against each branch's parent before the layer is complete.\n\nPlan the stack before editing. Build each concern on its owning branch instead of\nimplementing everything together and splitting the diff afterwards.\n\n## 1. Ground the work\n\nReplace `\u003Cskill-root>` with the directory containing this skill's `SKILL.md`,\nthen run the deterministic preflight before inspecting or changing files:\n\n```sh\nnode \"\u003Cskill-root>\u002Fscripts\u002Fpreflight.mjs\" --live --json\n```\n\nRun the command through the harness's host or escalated path when GitHub network\naccess is sandboxed. The script installs and configures nothing. A dirty worktree\nand disabled `rerere` are warnings; every failed required check blocks the run.\n\n- Read every supplied issue, spec, and direction in full. Fetch live tracker\n  state when the input names tickets.\n- Inspect the repository instructions, current branch, worktree, relevant code,\n  and available test and verification commands.\n- Preserve unrelated worktree changes. Stop only when overlap makes safe branch\n  ownership impossible or the requested behavior has material ambiguity.\n- Treat `gh stack init` as the authoritative repository-availability check when\n  preflight reports that the current branch is not yet stacked. Exit code 9\n  blocks the run before file edits.\n\nThis step is complete when every requested behavior and repository constraint is\naccounted for in the stack plan.\n\n## 2. Design the review story\n\nChoose the smallest dependency-ordered set of layers that makes each pull\nrequest understandable and useful:\n\n- Keep one coherent feature or project in a stack. Put independent work in\n  separate stacks rather than forcing a linear dependency.\n- For several issues, use one layer per issue only when issue boundaries also\n  form a clean dependency and review boundary.\n- For one large issue, split at real seams such as prerequisite refactoring,\n  domain behavior, integration, or a distinct consumer. Prefer end-to-end\n  behavior over arbitrary file or architecture layers.\n- Give every layer a one-sentence purpose. Each layer must be independently\n  reviewable, pass the checks its diff implicates, and leave its parent in a\n  coherent state.\n- Put shared foundations below their consumers. Assign each planned code change,\n  test, migration, and document to one owning layer before implementation.\n- Follow repository branch conventions. Otherwise use a shared topic prefix and\n  a specific concern suffix.\n\nProceed without a planning checkpoint unless a product choice would materially\nchange the stack or implementation.\n\n## 3. Create the stack first\n\nStart the bottom branch with `gh stack init \u003Cbranch>...` before writing code.\nImplement bottom to top. Add the next branch only after the current layer is\ncommitted and its worktree is clean.\n\nWhen continuing an existing stack, inspect it with `gh stack view --json` and\ncheck out the branch that owns a change before editing. After changing a lower\nlayer, rebase every branch above it and return to the top.\n\n## 4. Implement each layer\n\nFor each branch, apply a tight implementation loop:\n\n1. Run $tdd at the pre-agreed seams, one red-green vertical slice at a time.\n2. Typecheck and run focused tests regularly while implementing.\n3. Run every focused gate needed to show that this layer is independently green.\n4. Stage deliberately and commit the candidate layer to its current branch.\n5. Run $code-review against the parent branch. Fix every actionable finding on\n   the owning layer, rerun its gates, and commit the fixes with intentional\n   history.\n6. Confirm the layer has one review story and a clean worktree, then create the\n   next branch.\n\nTests for a layer's behavior belong in that layer. Reserve a final integration\nlayer for behavior that genuinely requires the complete stack.\n\n## 5. Verify the complete stack\n\nFrom the top branch, run the repository's full test suite once and every final\nverification lane implicated by the complete diff.\n\nAttribute a failure to its owning layer. Check out that branch, fix and commit it,\nrebase the upstack branches, return to the top, then rerun the affected checks and\nthe final verification. Inspect each branch diff against its parent so lower-layer\nwork has not leaked into a later review.\n\nThis step is complete only when every layer is reviewable on its own and the top\nof the stack passes the full verification contract.\n\n## 6. Submit the pull requests\n\nTreat invocation of this skill as authorization to push the planned stack and\ncreate its pull requests after local verification. It does not authorize merging.\n\n- Use `gh stack submit --auto` to create draft pull requests by default. Use\n  `--open` only when the user asked for ready-for-review pull requests.\n- Give each pull request a layer-scoped title and body. Include its purpose,\n  parent dependency, verification, issue links, and stack position.\n- Use `Closes #N` only on the layer that fully delivers that issue. Use a\n  non-closing issue reference on prerequisite or partial layers.\n- Confirm the final branch order, bases, pull request URLs, and states with\n  `gh stack view --json`.\n\n## Done\n\nReport the stack bottom to top with each pull request URL, its purpose, its local\nverification, and any remaining external checks. All planned layers are\ncommitted, locally green, submitted, and represented in the reported stack.\n",{"name":5,"description":7,"argument-hint":24,"compatibility":25,"disable-model-invocation":26},"\u003Cissue, spec, or direction>...","Requires Node.js, git, GitHub CLI with gh stack, and the gh-stack, tdd, and code-review skills.",true,"main","a79415595d32d9de44410555b992c907d2acd39b","skills\u002Fimplement-stack","https:\u002F\u002Fgithub.com\u002Fnick-neely\u002Fagent-skills","https:\u002F\u002Fgithub.com\u002Fnick-neely","nickneely.dev","Building web apps, breaking them, and fixing them again. React, Next.js, TypeScript, C#.","2026-11-14 04:25:18",{"source":8,"skillName":5,"commands":36,"prompt":46,"zipAvailable":26},[37,40,43],{"tool":38,"command":39},"npx","npx skills add nick-neely\u002Fagent-skills --skill implement-stack",{"tool":41,"command":42},"bunx","bunx skills add nick-neely\u002Fagent-skills --skill implement-stack",{"tool":44,"command":45},"pnpm","pnpm dlx skills add nick-neely\u002Fagent-skills --skill implement-stack","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fnick-neely\u002Fagent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fimplement-stack\u002FSKILL.md",[48,54],{"path":49,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":52,"sourceHtmlUrl":53},"agents\u002Fopenai.yaml","REFERENCE","参考文档",255,"https:\u002F\u002Fgithub.com\u002Fnick-neely\u002Fagent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fimplement-stack\u002Fagents\u002Fopenai.yaml",{"path":55,"resourceType":56,"resourceTypeDesc":57,"sizeBytes":58,"sourceHtmlUrl":59},"scripts\u002Fpreflight.mjs","SCRIPT","脚本",7496,"https:\u002F\u002Fgithub.com\u002Fnick-neely\u002Fagent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fimplement-stack\u002Fscripts\u002Fpreflight.mjs",[61,68,75,82,87,92],{"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},"01M7BECTZNYM56SQ1M304TC6JC","flow-walk","Fresh-eyes walk of one user flow in the running app, judging ease: friction, copy weight, confusing hierarchy and what can be removed. Use before code review when a change alters what a user sees or decides, and when asked to \"walk this flow\", \"try this as a user\" or get \"fresh eyes\" on a screen. The builder hands one user goal to a tester who knows nothing about the change, then sorts the report. It takes no acceptance criteria and keeps no run folder, only the report; checking acceptance criteria against requirements with retained evidence is the uat skill's job, and correctness belongs to tests and code review.","https:\u002F\u002Fgithub.com\u002Fnick-neely\u002Fagent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fflow-walk\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},"01M79PRF9536B79K1KDH3EC2ES","wrong","Wrong name fixture.","https:\u002F\u002Fgithub.com\u002Fnick-neely\u002Fagent-skills\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Fwrong-name\u002Fskills\u002Fright\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},"01M79PRE3HN1MB02EJ5STBKMET","sample","Sample skill for a fixture.","https:\u002F\u002Fgithub.com\u002Fnick-neely\u002Fagent-skills\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Funknown-frontmatter-key\u002Fskills\u002Fsample\u002FSKILL.md",[],[],{"skillNo":83,"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":84,"categories":85,"keywords":86,"publishedAt":19},"01M79PRD25SHAJTDB4JX87REEW","https:\u002F\u002Fgithub.com\u002Fnick-neely\u002Fagent-skills\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Funexpected-skill-subdirectory\u002Fskills\u002Fsample\u002FSKILL.md",[],[],{"skillNo":88,"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":89,"categories":90,"keywords":91,"publishedAt":19},"01M79PRBYYVMJ7KXZV11AQR584","https:\u002F\u002Fgithub.com\u002Fnick-neely\u002Fagent-skills\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Freadme-skill-list-mismatch\u002Fskills\u002Fsample\u002FSKILL.md",[],[],{"skillNo":93,"name":77,"nameZh":6,"description":94,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":95,"categories":96,"keywords":97,"publishedAt":19},"01M79PR53256JNXJ6RXXXJDTNV","\"aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa\"","https:\u002F\u002Fgithub.com\u002Fnick-neely\u002Fagent-skills\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Fquoted-overlong-folded-description\u002Fskills\u002Fsample\u002FSKILL.md",[],[]]