[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7DHXWAVHF5PQBDA8AMB3G0Z":3,"skill-same:01M7DHXWAVHF5PQBDA8AMB3G0Z":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":28,"repositoryHtmlUrl":29,"repositoryHomepageUrl":6,"ownerHtmlUrl":30,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":31,"install":32,"resources":44},"01M7DHXWAVHF5PQBDA8AMB3G0Z","dsh-implement-spec",null,"Implement the result of \u002Fdsh-to-spec and \u002Fdsh-to-tickets in code.","little3tar\u002Fdsh-mattpocock-skills","little3tar","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F138362670?v=4","01M7DHWNJBY5V6KXZXAP51DRK5","Kiraki","01M7DHWNK2NQAVJRAM3RB5NKV2",1,"MIT","https:\u002F\u002Fgithub.com\u002Flittle3tar\u002Fdsh-mattpocock-skills\u002Fblob\u002Fmain\u002Fskills\u002Fdsh-implement-spec\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: dsh-implement-spec\ndescription: \"Implement the result of \u002Fdsh-to-spec and \u002Fdsh-to-tickets in code.\"\ndisable-model-invocation: true\n---\n\nYou have been provided a spec. This spec should have tickets associated with it, describing how to implement the spec.\n\nThe issue tracker should have been provided to you. If not, tell the user to run `\u002Fdsh-setup-matt-pocock-skills`.\n\nThe goal is the entire spec implemented on a single **integration branch**, with every ticket resolved the way the issue tracker closes work.\n\nThe tickets are not a list of steps. They are a **task graph** with blocking relationships between them. This means there is always a **frontier** of tickets which are ready to be grabbed.\n\nStart every subagent with a fresh context window (`subagent`, not `subagent_fork`, which inherits this conversation).\n\nCommunication to and from subagents should be sparse. Communicate primarily through **context pointers**: to the spec, tickets, research notes, and previous commits. Don't duplicate information already available via pointers.\n\n**Implementer subagents** should be run in the background where possible for maximum concurrency.\n\n## Steps\n\n1. Read the spec and tickets to understand the task graph.\n\n2. (optional) Use an **exploration subagent** to conduct any exploration required by the tickets - relevant codebase files or external documentation. Ensure the exploration subagent can save files - it should save its markdown notes in a directory outside the repo, accessible by all future subagents. This lets **implementer subagents** focus on implementation rather than exploration.\n\n3. Create the integration branch. If the issue tracker closes work through PRs, or the user asks for one, open a draft PR after the first merge in step 5 (a branch with no commits ahead of main can't open one), marked as closing the spec and tickets.\n\n4. Use a fresh **implementer subagent** for each ticket, each in its own worktree on its own branch. Each implementer subagent:\n   - confirms its worktree is based on the integration branch before starting, and resets onto it if not;\n   - calls the `skill` tool with name `dsh-tdd` to build the ticket;\n   - merges the integration branch tip into its own branch before reporting done\n\n5. Once an **implementer subagent** completes, merge its work to the integration branch with a **merger subagent**.\n\n6. If this changes the **frontier** of available tickets, kick off more **implementer subagents** to work on the new tickets. This allows for maximum concurrency.\n\n7. Once all tickets are complete, call the `skill` tool with name `dsh-code-review` on the integration branch. Fix all issues raised by the code review in a single fresh **implementer subagent**.\n\n8. If a draft PR exists, mark it ready for review. Otherwise, resolve each ticket the way the issue tracker closes work, and report the integration branch.\n\n9. Clean up all **implementer subagent** worktrees.\n","You have been provided a spec. This spec should have tickets associated with it, describing how to implement the spec.\n\nThe issue tracker should have been provided to you. If not, tell the user to run `\u002Fdsh-setup-matt-pocock-skills`.\n\nThe goal is the entire spec implemented on a single **integration branch**, with every ticket resolved the way the issue tracker closes work.\n\nThe tickets are not a list of steps. They are a **task graph** with blocking relationships between them. This means there is always a **frontier** of tickets which are ready to be grabbed.\n\nStart every subagent with a fresh context window (`subagent`, not `subagent_fork`, which inherits this conversation).\n\nCommunication to and from subagents should be sparse. Communicate primarily through **context pointers**: to the spec, tickets, research notes, and previous commits. Don't duplicate information already available via pointers.\n\n**Implementer subagents** should be run in the background where possible for maximum concurrency.\n\n## Steps\n\n1. Read the spec and tickets to understand the task graph.\n\n2. (optional) Use an **exploration subagent** to conduct any exploration required by the tickets - relevant codebase files or external documentation. Ensure the exploration subagent can save files - it should save its markdown notes in a directory outside the repo, accessible by all future subagents. This lets **implementer subagents** focus on implementation rather than exploration.\n\n3. Create the integration branch. If the issue tracker closes work through PRs, or the user asks for one, open a draft PR after the first merge in step 5 (a branch with no commits ahead of main can't open one), marked as closing the spec and tickets.\n\n4. Use a fresh **implementer subagent** for each ticket, each in its own worktree on its own branch. Each implementer subagent:\n   - confirms its worktree is based on the integration branch before starting, and resets onto it if not;\n   - calls the `skill` tool with name `dsh-tdd` to build the ticket;\n   - merges the integration branch tip into its own branch before reporting done\n\n5. Once an **implementer subagent** completes, merge its work to the integration branch with a **merger subagent**.\n\n6. If this changes the **frontier** of available tickets, kick off more **implementer subagents** to work on the new tickets. This allows for maximum concurrency.\n\n7. Once all tickets are complete, call the `skill` tool with name `dsh-code-review` on the integration branch. Fix all issues raised by the code review in a single fresh **implementer subagent**.\n\n8. If a draft PR exists, mark it ready for review. Otherwise, resolve each ticket the way the issue tracker closes work, and report the integration branch.\n\n9. Clean up all **implementer subagent** worktrees.\n",{"name":5,"description":7,"disable-model-invocation":24},true,"main","755dffa8c3a8f81f593c83adb0bbce5e65a7f0fa","skills\u002Fdsh-implement-spec",0,"https:\u002F\u002Fgithub.com\u002Flittle3tar\u002Fdsh-mattpocock-skills","https:\u002F\u002Fgithub.com\u002Flittle3tar","2026-11-06 13:41:57",{"source":8,"skillName":5,"commands":33,"prompt":43,"zipAvailable":24},[34,37,40],{"tool":35,"command":36},"npx","npx skills add little3tar\u002Fdsh-mattpocock-skills --skill dsh-implement-spec",{"tool":38,"command":39},"bunx","bunx skills add little3tar\u002Fdsh-mattpocock-skills --skill dsh-implement-spec",{"tool":41,"command":42},"pnpm","pnpm dlx skills add little3tar\u002Fdsh-mattpocock-skills --skill dsh-implement-spec","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Flittle3tar\u002Fdsh-mattpocock-skills\u002Fblob\u002Fmain\u002Fskills\u002Fdsh-implement-spec\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},"01M7DJ04ZKSD81GZ111BWZKT94","dsh-writing-for-agents","Writing documents for agents. Use when creating or editing skills, or modifying AGENTS.md or CLAUDE.md.","https:\u002F\u002Fgithub.com\u002Flittle3tar\u002Fdsh-mattpocock-skills\u002Fblob\u002Fmain\u002Fskills\u002Fdsh-writing-for-agents\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},"01M7DHZZ973HZFWZQ83EZMBW9S","dsh-wizard","Generate an interactive bash wizard that walks a human through steps only they can perform. Use when provisioning infrastructure, setting up credentials or CI secrets, walking an unfamiliar third-party dashboard, or running a one-off migration or cutover. Don't invoke this for steps the agent can perform itself.","https:\u002F\u002Fgithub.com\u002Flittle3tar\u002Fdsh-mattpocock-skills\u002Fblob\u002Fmain\u002Fskills\u002Fdsh-wizard\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},"01M7DHZV1YMTVD3ZFK5AGV2AZX","dsh-wayfinder","Plan a huge chunk of work (more than one agent session can hold) as a shared map of decision tickets on your issue tracker, and resolve them one at a time until the way to the destination is clear.","https:\u002F\u002Fgithub.com\u002Flittle3tar\u002Fdsh-mattpocock-skills\u002Fblob\u002Fmain\u002Fskills\u002Fdsh-wayfinder\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},"01M7DHZQE17DZG7EFGPC0WJM59","dsh-wait-what","Stop. That last message did not land: re-pitch it.","https:\u002F\u002Fgithub.com\u002Flittle3tar\u002Fdsh-mattpocock-skills\u002Fblob\u002Fmain\u002Fskills\u002Fdsh-wait-what\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},"01M7DHZJFYW0CNXQJGQQ4JFFZ4","dsh-triage","Move issues and external PRs through a state machine of triage roles, categorise, verify, grill if needed, and write agent-ready briefs.","https:\u002F\u002Fgithub.com\u002Flittle3tar\u002Fdsh-mattpocock-skills\u002Fblob\u002Fmain\u002Fskills\u002Fdsh-triage\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},"01M7DHZD00BXP9TBF3GFZAY0FA","dsh-to-tickets","Break a plan, spec, or the current conversation into a set of tracer-bullet tickets, each declaring its blocking edges, published to the configured tracker (edges as text in one file per ticket locally, or native blocking links on a real tracker).","https:\u002F\u002Fgithub.com\u002Flittle3tar\u002Fdsh-mattpocock-skills\u002Fblob\u002Fmain\u002Fskills\u002Fdsh-to-tickets\u002FSKILL.md",[],[]]