[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7F761015RBDN2SPFK6EP2WQ":3,"skill-same:01M7F761015RBDN2SPFK6EP2WQ":52},{"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":30,"ownerHtmlUrl":31,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":32,"install":33,"resources":45},"01M7F761015RBDN2SPFK6EP2WQ","implement-spec",null,"Implement the result of \u002Fto-spec and \u002Fto-tickets in code.","alexj11324\u002FMikka","alexj11324","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F183887963?v=4","01M7F72W5NYK4AXQCEH0PZM81E","Zhixuan Jiang","01M7F72W69V101X48H9PZVBB46",87,"AGPL-3.0","https:\u002F\u002Fgithub.com\u002Falexj11324\u002FMikka\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fimplement-spec\u002FSKILL.md",[],[],"2026-11-16 10:05:34",false,"---\nname: implement-spec\ndescription: \"Implement the result of \u002Fto-spec and \u002Fto-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 `\u002Fsetup-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.\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 `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 `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 `\u002Fsetup-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.\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 `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 `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","4ae55457c0230cc1b0d4ab22ba0ac86662b8202d",".claude\u002Fskills\u002Fimplement-spec",11,"https:\u002F\u002Fgithub.com\u002Falexj11324\u002FMikka","https:\u002F\u002Faspectlylabs.com\u002Fmikka","https:\u002F\u002Fgithub.com\u002Falexj11324","2026-11-15 16:49:24",{"source":8,"skillName":5,"commands":34,"prompt":44,"zipAvailable":24},[35,38,41],{"tool":36,"command":37},"npx","npx skills add alexj11324\u002FMikka --skill implement-spec",{"tool":39,"command":40},"bunx","bunx skills add alexj11324\u002FMikka --skill implement-spec",{"tool":42,"command":43},"pnpm","pnpm dlx skills add alexj11324\u002FMikka --skill implement-spec","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Falexj11324\u002FMikka\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fimplement-spec\u002FSKILL.md",[46],{"path":47,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":50,"sourceHtmlUrl":51},"agents\u002Fopenai.yaml","REFERENCE","参考文档",168,"https:\u002F\u002Fgithub.com\u002Falexj11324\u002FMikka\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fimplement-spec\u002Fagents\u002Fopenai.yaml",[53,59,65,72,79,86],{"skillNo":54,"name":55,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":56,"categories":57,"keywords":58,"publishedAt":19},"01M7F7DR2H1H14E5BJ8FFG73A3","run-report","https:\u002F\u002Fgithub.com\u002Falexj11324\u002FMikka\u002Fblob\u002Fmain\u002Flib\u002Fself-improvement\u002Fskills\u002Frun-report\u002FSKILL.md",[],[],{"skillNo":60,"name":61,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":62,"categories":63,"keywords":64,"publishedAt":19},"01M7F7DN7QRPJM3QGP20AYQHRA","source-checking","https:\u002F\u002Fgithub.com\u002Falexj11324\u002FMikka\u002Fblob\u002Fmain\u002Fagents\u002Fresearch-example\u002Fskills\u002Fsource-checking\u002FSKILL.md",[],[],{"skillNo":66,"name":67,"nameZh":6,"description":68,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":69,"categories":70,"keywords":71,"publishedAt":19},"01M7F7DHXRSSGKW4CXVRTYTHRC","writing-shape","Writing, exploit: shape raw material into an article, paragraph by paragraph.","https:\u002F\u002Fgithub.com\u002Falexj11324\u002FMikka\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fwriting-shape\u002FSKILL.md",[],[],{"skillNo":73,"name":74,"nameZh":6,"description":75,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":76,"categories":77,"keywords":78,"publishedAt":19},"01M7F7DAATWYFV4YFV0NNZ507V","writing-fragments","Writing, explore: mine raw fragments, no structure yet.","https:\u002F\u002Fgithub.com\u002Falexj11324\u002FMikka\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fwriting-fragments\u002FSKILL.md",[],[],{"skillNo":80,"name":81,"nameZh":6,"description":82,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":83,"categories":84,"keywords":85,"publishedAt":19},"01M7F7D3TJ6E75PEFWNVXYREHZ","writing-for-agents","Writing documents for agents. Use when creating or editing skills, or modifying AGENTS.md or CLAUDE.md.","https:\u002F\u002Fgithub.com\u002Falexj11324\u002FMikka\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fwriting-for-agents\u002FSKILL.md",[],[],{"skillNo":87,"name":88,"nameZh":6,"description":89,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":90,"categories":91,"keywords":92,"publishedAt":19},"01M7F7CYAB0GYT0R5KXY4SEPR8","writing-beats","Writing, exploit; assemble raw material into a journey of beats, grounding each term before a beat leans on it.","https:\u002F\u002Fgithub.com\u002Falexj11324\u002FMikka\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fwriting-beats\u002FSKILL.md",[],[]]