[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M79H7NVA83YC2BCSMAFNEASK":3,"skill-same:01M79H7NVA83YC2BCSMAFNEASK":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},"01M79H7NVA83YC2BCSMAFNEASK","implement",null,"Implement one eligible Workbench ticket through verified remote recovery.","KaydenClark\u002FFoundry","KaydenClark","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F26465021?v=4","01M79H31FNE2HKKE40PPQA5VCC","Kayden Clark","01M79H31GPGM16FRE9M4QXJT4T",0,"MIT","https:\u002F\u002Fgithub.com\u002FKaydenClark\u002FFoundry\u002Fblob\u002Fmain\u002Frecovery\u002Flegacy-skill-snapshot\u002Fimplement\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: implement\ndescription: Implement one eligible Workbench ticket through verified remote recovery.\ndisable-model-invocation: true\n---\n\nImplement one eligible ticket from the assigned stable `SPEC.md`. One invocation\nowns one ticket and one durable writer lane.\n\n## 1. Situate the slice\n\nVerify the repository root, branch, remote, upstream, and dirty state. Read the\nnearest `AGENTS.md` and its `RUNBOOK.md`, then run:\n\n```bash\nnode tools\u002Fspec-workbench.mjs doctor\nnode tools\u002Fspec-workbench.mjs next --json\nnode tools\u002Fspec-workbench.mjs show S-###\n```\n\nContinue only when `next` returns the assigned ticket as ready or resumable and\nthe working tree can be safely attributed. For a ready slice, claim it:\n\n```bash\nnode tools\u002Fspec-workbench.mjs claim S-### --agent NAME\n```\n\nThe slice is situated when one eligible ticket, its acceptance boundary, its\npublic testing seam, and its single writer are explicit.\n\n## 2. Drive the behavior\n\nUse red\u002Fgreen\u002Frefactor at the agreed seam:\n\n1. Add or change the smallest durable test that expresses the ticket behavior.\n2. Run it and observe the expected red failure.\n3. Implement the smallest change that turns it green.\n4. Refactor while the focused test stays green.\n\nRun focused checks during the loop. Finish with every project-owned verification\ncommand required by `RUNBOOK.md`. The behavior is driven when the expected red\nand green results are named and the full required gate is green.\n\n## 3. Document and checkpoint\n\nUpdate the owning documentation named by `AGENTS.md`; keep capability state and\nproof in the assigned spec and keep `TASKBOARD.md` a generated projection. Run\nthe required verification and create a truthful in-progress checkpoint while\nthe ticket remains in progress; commit and push it, then compare the local SHA\nwith the remote branch SHA.\n\nRecord the comparison base as `BASE_SHA` and the remotely verified checkpoint as\n`HEAD_SHA`. This step is complete only when the remote is the recovery point for\nthe exact code, tests, documentation, and in-progress spec state under review.\n\n## 4. Review the immutable checkpoint\n\nRun `\u002Fcode-review` as a separate review task against `BASE_SHA` and `HEAD_SHA`.\nThat fixed immutable-SHA review must inspect the pushed commit, not later\nworking-tree state.\n\nResolve each in-scope finding through the same red\u002Fgreen loop. Update its owning\ndocumentation, create and push a new truthful checkpoint, verify the new remote\nSHA, and re-review the newly fixed `BASE_SHA` to `HEAD_SHA` range. Repeat until\nthe exact-head review is green with no unresolved in-scope finding.\n\nIf review cannot finish, leave the ticket in progress and yield only after its\nlatest truthful checkpoint is remotely recoverable.\n\n## 5. Close and recover remotely\n\nOnly after the exact-head review is green, close the ticket with its acceptance\nand proof:\n\n```bash\nnode tools\u002Fspec-workbench.mjs close S-### \\\n  --proof \"NAMED VERIFICATION\" \\\n  --docs \"DOCS UPDATED OR Docs checked; no update needed + reason\" \\\n  --remaining-gap \"GAP OR none\"\nnode tools\u002Fspec-workbench.mjs render\nnode tools\u002Fspec-workbench.mjs doctor\n```\n\nCommit the close evidence and generated projection, make the final push, and\nverify the remote branch resolves to that local commit. If the ticket remains\nincomplete, its in-progress checkpoint is the handoff; closing is not truthful.\n\nAutomated delivery stops at `integration` after the repository's review\ngates pass. The owner controls promotion from integration to the release branch.\n\nThe invocation is complete only when the worktree state is accounted for and\nthe pushed remote commit is the recovery point.\n","Implement one eligible ticket from the assigned stable `SPEC.md`. One invocation\nowns one ticket and one durable writer lane.\n\n## 1. Situate the slice\n\nVerify the repository root, branch, remote, upstream, and dirty state. Read the\nnearest `AGENTS.md` and its `RUNBOOK.md`, then run:\n\n```bash\nnode tools\u002Fspec-workbench.mjs doctor\nnode tools\u002Fspec-workbench.mjs next --json\nnode tools\u002Fspec-workbench.mjs show S-###\n```\n\nContinue only when `next` returns the assigned ticket as ready or resumable and\nthe working tree can be safely attributed. For a ready slice, claim it:\n\n```bash\nnode tools\u002Fspec-workbench.mjs claim S-### --agent NAME\n```\n\nThe slice is situated when one eligible ticket, its acceptance boundary, its\npublic testing seam, and its single writer are explicit.\n\n## 2. Drive the behavior\n\nUse red\u002Fgreen\u002Frefactor at the agreed seam:\n\n1. Add or change the smallest durable test that expresses the ticket behavior.\n2. Run it and observe the expected red failure.\n3. Implement the smallest change that turns it green.\n4. Refactor while the focused test stays green.\n\nRun focused checks during the loop. Finish with every project-owned verification\ncommand required by `RUNBOOK.md`. The behavior is driven when the expected red\nand green results are named and the full required gate is green.\n\n## 3. Document and checkpoint\n\nUpdate the owning documentation named by `AGENTS.md`; keep capability state and\nproof in the assigned spec and keep `TASKBOARD.md` a generated projection. Run\nthe required verification and create a truthful in-progress checkpoint while\nthe ticket remains in progress; commit and push it, then compare the local SHA\nwith the remote branch SHA.\n\nRecord the comparison base as `BASE_SHA` and the remotely verified checkpoint as\n`HEAD_SHA`. This step is complete only when the remote is the recovery point for\nthe exact code, tests, documentation, and in-progress spec state under review.\n\n## 4. Review the immutable checkpoint\n\nRun `\u002Fcode-review` as a separate review task against `BASE_SHA` and `HEAD_SHA`.\nThat fixed immutable-SHA review must inspect the pushed commit, not later\nworking-tree state.\n\nResolve each in-scope finding through the same red\u002Fgreen loop. Update its owning\ndocumentation, create and push a new truthful checkpoint, verify the new remote\nSHA, and re-review the newly fixed `BASE_SHA` to `HEAD_SHA` range. Repeat until\nthe exact-head review is green with no unresolved in-scope finding.\n\nIf review cannot finish, leave the ticket in progress and yield only after its\nlatest truthful checkpoint is remotely recoverable.\n\n## 5. Close and recover remotely\n\nOnly after the exact-head review is green, close the ticket with its acceptance\nand proof:\n\n```bash\nnode tools\u002Fspec-workbench.mjs close S-### \\\n  --proof \"NAMED VERIFICATION\" \\\n  --docs \"DOCS UPDATED OR Docs checked; no update needed + reason\" \\\n  --remaining-gap \"GAP OR none\"\nnode tools\u002Fspec-workbench.mjs render\nnode tools\u002Fspec-workbench.mjs doctor\n```\n\nCommit the close evidence and generated projection, make the final push, and\nverify the remote branch resolves to that local commit. If the ticket remains\nincomplete, its in-progress checkpoint is the handoff; closing is not truthful.\n\nAutomated delivery stops at `integration` after the repository's review\ngates pass. The owner controls promotion from integration to the release branch.\n\nThe invocation is complete only when the worktree state is accounted for and\nthe pushed remote commit is the recovery point.\n",{"name":5,"description":7,"disable-model-invocation":24},true,"main","9381af33e9db4f69f7c4f83ded287e23e109c7c1","recovery\u002Flegacy-skill-snapshot\u002Fimplement","https:\u002F\u002Fgithub.com\u002FKaydenClark\u002FFoundry","https:\u002F\u002Fgithub.com\u002FKaydenClark","https:\u002F\u002Fkayden-clark.vercel.app\u002F","Building simple systems to solve complex problems","2026-09-05 15:28:09",{"source":8,"skillName":5,"commands":34,"prompt":44,"zipAvailable":24},[35,38,41],{"tool":36,"command":37},"npx","npx skills add KaydenClark\u002FFoundry --skill implement",{"tool":39,"command":40},"bunx","bunx skills add KaydenClark\u002FFoundry --skill implement",{"tool":42,"command":43},"pnpm","pnpm dlx skills add KaydenClark\u002FFoundry --skill implement","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FKaydenClark\u002FFoundry\u002Fblob\u002Fmain\u002Frecovery\u002Flegacy-skill-snapshot\u002Fimplement\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},"01M79H8BQMY5ZFKYHRQ12YT67B","writing-great-skills","Reference for writing and editing skills well — the vocabulary and principles that make a skill predictable.","https:\u002F\u002Fgithub.com\u002FKaydenClark\u002FFoundry\u002Fblob\u002Fmain\u002Frecovery\u002Flegacy-skill-snapshot\u002Fwriting-great-skills\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},"01M79H88YTKNDMAPEHS9HDM51E","update-harness","Update a project to the current canonical LLM Workbench harness without losing project-specific controls, work state, or proof.","https:\u002F\u002Fgithub.com\u002FKaydenClark\u002FFoundry\u002Fblob\u002Fmain\u002Frecovery\u002Flegacy-skill-snapshot\u002Fupdate-harness\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},"01M79H867VMC0SQ5A1687SCGCF","tracer-bullet","Cut a capability into vertical tracer-bullet slices that each pierce every layer of a project's stack, then order, scope, and assign them.","https:\u002F\u002Fgithub.com\u002FKaydenClark\u002FFoundry\u002Fblob\u002Fmain\u002Frecovery\u002Flegacy-skill-snapshot\u002Ftracer-bullet\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},"01M79H84D6KN135D17505TFEXH","to-tickets","Break an assigned Workbench spec into dependency-aware tracer-bullet tickets.","https:\u002F\u002Fgithub.com\u002FKaydenClark\u002FFoundry\u002Fblob\u002Fmain\u002Frecovery\u002Flegacy-skill-snapshot\u002Fto-tickets\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},"01M79H82Q2GFBBCQZ4ZHHHYDW1","to-spec","Turn an already-settled conversation into one stable Workbench capability spec without restarting the interview.","https:\u002F\u002Fgithub.com\u002FKaydenClark\u002FFoundry\u002Fblob\u002Fmain\u002Frecovery\u002Flegacy-skill-snapshot\u002Fto-spec\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},"01M79H80SAT2SWTSF8HA4J8X34","to-docs","Route settled conversation truth into existing Workbench documentation owners without restarting discovery or creating another store.","https:\u002F\u002Fgithub.com\u002FKaydenClark\u002FFoundry\u002Fblob\u002Fmain\u002Frecovery\u002Flegacy-skill-snapshot\u002Fto-docs\u002FSKILL.md",[],[]]