[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7FEENCBZGVDN2RGQ6DYWZHT":3,"skill-same:01M7FEENCBZGVDN2RGQ6DYWZHT":52},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":18,"linkOnly":19,"markdownContent":20,"markdownBody":21,"frontMatter":22,"refName":24,"commitSha":25,"skillDirectory":26,"forksCount":27,"repositoryHtmlUrl":28,"repositoryHomepageUrl":29,"ownerHtmlUrl":30,"ownerBlogUrl":31,"ownerDescription":6,"updatedAt":32,"install":33,"resources":45},"01M7FEENCBZGVDN2RGQ6DYWZHT","implement-spec",null,"Implement the result of \u002Fto-spec and \u002Fto-tickets in code.","KenSuh\u002Fopen-agent-harness","KenSuh","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F275614337?v=4","01M7FECQPZX8TW9GKH66NR9STC","01M7FECQRAPP7AHZEE46G8QWD7",33,"MIT","https:\u002F\u002Fgithub.com\u002FKenSuh\u002Fopen-agent-harness\u002Fblob\u002Fmain\u002Fskills\u002Fmattpocock-skills\u002Fengineering\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\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 **implementer subagents** to implement 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 **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\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 **implementer subagents** to implement 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 **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":23},true,"main","62613ef388a09930e89f8f89bb28850bbd1b74ed","skills\u002Fmattpocock-skills\u002Fengineering\u002Fimplement-spec",3,"https:\u002F\u002Fgithub.com\u002FKenSuh\u002Fopen-agent-harness","https:\u002F\u002Foah.rodeo","https:\u002F\u002Fgithub.com\u002FKenSuh","gearup.kr","2026-11-11 10:14:20",{"source":8,"skillName":5,"commands":34,"prompt":44,"zipAvailable":23},[35,38,41],{"tool":36,"command":37},"npx","npx skills add KenSuh\u002Fopen-agent-harness --skill implement-spec",{"tool":39,"command":40},"bunx","bunx skills add KenSuh\u002Fopen-agent-harness --skill implement-spec",{"tool":42,"command":43},"pnpm","pnpm dlx skills add KenSuh\u002Fopen-agent-harness --skill implement-spec","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FKenSuh\u002Fopen-agent-harness\u002Fblob\u002Fmain\u002Fskills\u002Fmattpocock-skills\u002Fengineering\u002Fimplement-spec\u002FSKILL.md",[46],{"path":47,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":50,"sourceHtmlUrl":51},"agents\u002Fopenai.yaml","REFERENCE","参考文档",168,"https:\u002F\u002Fgithub.com\u002FKenSuh\u002Fopen-agent-harness\u002Fblob\u002Fmain\u002Fskills\u002Fmattpocock-skills\u002Fengineering\u002Fimplement-spec\u002Fagents\u002Fopenai.yaml",[53,61,70,77,84,91],{"skillNo":54,"name":55,"nameZh":6,"description":56,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":57,"sourceHtmlUrl":58,"categories":59,"keywords":60,"publishedAt":18},"01M7FEK80Y379HPDBYRVHBWSFC","typesafe-ai","Build AI-powered software with TypeSafe: small units of AI intelligence you can use like programming primitives. Its System One models, including Jev, turn natural language and application state into typed judgments and probabilities that code can combine. Use when a feature needs programmable common sense, when brainstorming what AI could make possible in an app, or when an LLM prompt-and-parse step could become a structured decision. Applications include routing, ranking, extraction, verification, and interactive experiences; these are starting points, not the limits. Read live docs and cookbooks to find useful patterns and discover new combinations.","https:\u002F\u002Fgithub.com\u002FKenSuh\u002Fopen-agent-harness\u002Fblob\u002Fmain\u002Fskills\u002Ftypesafe-ai\u002FLICENSE","https:\u002F\u002Fgithub.com\u002FKenSuh\u002Fopen-agent-harness\u002Fblob\u002Fmain\u002Fskills\u002Ftypesafe-ai\u002FSKILL.md",[],[],{"skillNo":62,"name":63,"nameZh":6,"description":64,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":65,"licenseFileUrl":66,"sourceHtmlUrl":67,"categories":68,"keywords":69,"publishedAt":18},"01M7FEK08DQCTC7ZDC8FA9A3WC","skill-creator","Create new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy.","Apache-2.0","https:\u002F\u002Fgithub.com\u002FKenSuh\u002Fopen-agent-harness\u002Fblob\u002Fmain\u002Fskills\u002Fskill-creator\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002FKenSuh\u002Fopen-agent-harness\u002Fblob\u002Fmain\u002Fskills\u002Fskill-creator\u002FSKILL.md",[],[],{"skillNo":71,"name":72,"nameZh":6,"description":73,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":74,"categories":75,"keywords":76,"publishedAt":18},"01M7FEJQMQ6Z429TYF78XPP5X7","ponytail","Forces the laziest solution that actually works, simplest, shortest, most minimal. Channels a senior dev who has seen everything: question whether the task needs to exist at all (YAGNI), reach for the standard library before custom code, native platform features before dependencies, one line before fifty. Supports intensity levels: lite, full (default), ultra. Use on ANY coding task: writing, adding, refactoring, fixing, reviewing, or designing code, and choosing libraries or dependencies. Also use whenever the user says \"ponytail\", \"be lazy\", \"lazy mode\", \"simplest solution\", \"minimal solution\", \"yagni\", \"do less\", or \"shortest path\", or complains about over-engineering, bloat, boilerplate, or unnecessary dependencies. Do NOT use for non-coding requests (general knowledge, prose, translation, summaries, recipes).","https:\u002F\u002Fgithub.com\u002FKenSuh\u002Fopen-agent-harness\u002Fblob\u002Fmain\u002Fskills\u002Fponytail\u002Fponytail\u002FSKILL.md",[],[],{"skillNo":78,"name":79,"nameZh":6,"description":80,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":81,"categories":82,"keywords":83,"publishedAt":18},"01M7FEJK0SWY87WP0QMV5KWDTJ","ponytail-review","Code review focused exclusively on over-engineering. Finds what to delete: reinvented standard library, unneeded dependencies, speculative abstractions, dead flexibility. One line per finding: location, what to cut, what replaces it. Use when the user says \"review for over-engineering\", \"what can we delete\", \"is this over-engineered\", \"simplify review\", or invokes \u002Fponytail-review. Complements correctness-focused review, this one only hunts complexity.","https:\u002F\u002Fgithub.com\u002FKenSuh\u002Fopen-agent-harness\u002Fblob\u002Fmain\u002Fskills\u002Fponytail\u002Fponytail-review\u002FSKILL.md",[],[],{"skillNo":85,"name":86,"nameZh":6,"description":87,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":88,"categories":89,"keywords":90,"publishedAt":18},"01M7FEJG5SDCZ9DY8JA9M4YZP6","ponytail-help","Quick-reference card for all ponytail modes, skills, and commands. One-shot display, not a persistent mode. Trigger: \u002Fponytail-help, \"ponytail help\", \"what ponytail commands\", \"how do I use ponytail\".","https:\u002F\u002Fgithub.com\u002FKenSuh\u002Fopen-agent-harness\u002Fblob\u002Fmain\u002Fskills\u002Fponytail\u002Fponytail-help\u002FSKILL.md",[],[],{"skillNo":92,"name":93,"nameZh":6,"description":94,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":95,"categories":96,"keywords":97,"publishedAt":18},"01M7FEJCAQC4JYMB75Y8WGJKJ7","ponytail-gain","Show ponytail's measured impact as a compact scoreboard: less code, less cost, more speed, from the benchmark medians. One-shot display, not a persistent mode, and not a per-repo number. Trigger: \u002Fponytail-gain, \"ponytail gain\", \"what does ponytail save\", \"show ponytail impact\", \"ponytail scoreboard\".","https:\u002F\u002Fgithub.com\u002FKenSuh\u002Fopen-agent-harness\u002Fblob\u002Fmain\u002Fskills\u002Fponytail\u002Fponytail-gain\u002FSKILL.md",[],[]]