[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6KX2544HCCQ61N1BEB52JSH":3,"skill-same:01M6KX2544HCCQ61N1BEB52JSH":75},{"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":39,"linkOnly":40,"markdownContent":41,"markdownBody":42,"frontMatter":43,"refName":46,"commitSha":47,"skillDirectory":48,"forksCount":49,"repositoryHtmlUrl":50,"repositoryHomepageUrl":6,"ownerHtmlUrl":51,"ownerBlogUrl":52,"ownerDescription":53,"updatedAt":54,"install":55,"resources":68},"01M6KX2544HCCQ61N1BEB52JSH","implement-spec",null,"Build a whole spec's tickets in parallel subagents, onto one integration branch.","dougborg\u002Fharness-kit","dougborg","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F1261222?v=4","01M6KWS4PB51EYD4ZDJJSGNGB2","Doug Borg","01M6KWS4T8ZZW6SX5QZS9B5BN2",0,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fdougborg\u002Fharness-kit\u002Fblob\u002Fmain\u002Fskills\u002Forchestration\u002Fimplement-spec\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38],"implement","spec","implement spec","shared","git log","switch","log","ready","view","branch","parallel","gh","git push","gh pr","Bash","gh issue","push","git branch","git merge","pr","2026-11-10 10:12:30",false,"---\nname: implement-spec\ndescription: Build a whole spec's tickets in parallel subagents, onto one integration branch.\nargument-hint: \"\u003Cspec issue>\"\nallowed-tools: Read, Grep, Glob, Bash(gh issue *), Bash(gh pr create*), Bash(gh pr ready*), Bash(gh pr view*), Bash(git switch*), Bash(git branch*), Bash(git merge*), Bash(git push*), Bash(git worktree*), Bash(git status*), Bash(git log*), Bash(\u003Cshared-scripts-dir>\u002Fsub-issue-frontier.sh*)\n---\n\n# Implement Spec\n\nBuild every ticket of a spec, as filed by the to-tickets skill, onto one\n**integration branch**. The tickets aren't a list but a **task graph**: each\nnames the tickets that block it, so there is always a **frontier** of tickets\nready to start. Run implementers across the frontier in parallel; as each\nlands, the frontier moves.\n\nThis needs subagents that can work in their own git worktrees (Claude Code's\nAgent tool with worktree isolation, or Codex's spawned agents). Without them,\nwork the tickets one at a time with the implement skill instead.\n\nKeep traffic to and from subagents small. Point at the spec, the ticket, notes,\nand commits rather than pasting their contents.\n\n## 1. Read the graph\n\nRead the spec and list its tickets with\n`\u003Cshared-scripts-dir>\u002Fsub-issue-frontier.sh \u003Cspec>`. On Claude Code, call the\nSkill tool with \"budget\" before a large fan-out. Done when you know the\nfrontier and how many implementers to run at once.\n\n## 2. Explore once (optional)\n\nWhen several tickets need the same reading (code areas, external docs), have\none exploration subagent write its notes to a directory outside the repo that\nevery later subagent can read. Done when the notes' path is ready to hand to\nthe implementers.\n\n## 3. Create the integration branch\n\nBranch from the base and push it. Done when the branch exists on the remote.\n\n## 4. Run implementers across the frontier\n\nFor each frontier ticket, claim it (`gh issue edit \u003Cn> --add-assignee @me`),\nthen re-read its assignees: assigning never fails when someone else is already\non it, so if anyone else is, leave it and take the next. Start an implementer\nsubagent for each claimed ticket in its own worktree and branch, in the\nbackground where the host allows. Each implementer:\n\n- checks that its worktree is based on the integration branch, and resets onto\n  it if not;\n- calls the Skill tool with \"tdd\" to build the ticket, and calls it again with\n  \"minimal-change\" before adding a dependency or an abstraction;\n- runs the project's verification;\n- merges the integration branch's latest tip into its own branch before\n  reporting done.\n\nDone when every frontier ticket has an implementer running or reported done\n(or blocked, with the reason).\n\n## 5. Merge as they land\n\nWhen an implementer reports done, merge its branch into the integration branch\nwith a merger subagent, resolving conflicts there, and run verification on the\nresult. After the first merge, if the repo closes work through pull requests\n(or the user wants one), open a draft PR from the integration branch that\ncloses the spec and its tickets, with a body in the pr-body skill's shape.\nOtherwise call the Skill tool with \"issue-close\" for each ticket as it lands.\nIf a merge unblocks tickets, start implementers for the new frontier. Done when\nevery ticket is merged and either linked from the draft PR or closed.\n\n## 6. Review and finish\n\nWith a draft PR, mark it ready, then call the Skill tool with \"review-pr\",\nasking for the agent review (its standards and spec passes against the whole\nspec), and fix their findings\nin a single implementer subagent. Without one, report the integration branch.\nDone when the review gate is met (or the branch is reported), CI is green, and\nevery implementer worktree is removed (`git worktree remove`).\n","# Implement Spec\n\nBuild every ticket of a spec, as filed by the to-tickets skill, onto one\n**integration branch**. The tickets aren't a list but a **task graph**: each\nnames the tickets that block it, so there is always a **frontier** of tickets\nready to start. Run implementers across the frontier in parallel; as each\nlands, the frontier moves.\n\nThis needs subagents that can work in their own git worktrees (Claude Code's\nAgent tool with worktree isolation, or Codex's spawned agents). Without them,\nwork the tickets one at a time with the implement skill instead.\n\nKeep traffic to and from subagents small. Point at the spec, the ticket, notes,\nand commits rather than pasting their contents.\n\n## 1. Read the graph\n\nRead the spec and list its tickets with\n`\u003Cshared-scripts-dir>\u002Fsub-issue-frontier.sh \u003Cspec>`. On Claude Code, call the\nSkill tool with \"budget\" before a large fan-out. Done when you know the\nfrontier and how many implementers to run at once.\n\n## 2. Explore once (optional)\n\nWhen several tickets need the same reading (code areas, external docs), have\none exploration subagent write its notes to a directory outside the repo that\nevery later subagent can read. Done when the notes' path is ready to hand to\nthe implementers.\n\n## 3. Create the integration branch\n\nBranch from the base and push it. Done when the branch exists on the remote.\n\n## 4. Run implementers across the frontier\n\nFor each frontier ticket, claim it (`gh issue edit \u003Cn> --add-assignee @me`),\nthen re-read its assignees: assigning never fails when someone else is already\non it, so if anyone else is, leave it and take the next. Start an implementer\nsubagent for each claimed ticket in its own worktree and branch, in the\nbackground where the host allows. Each implementer:\n\n- checks that its worktree is based on the integration branch, and resets onto\n  it if not;\n- calls the Skill tool with \"tdd\" to build the ticket, and calls it again with\n  \"minimal-change\" before adding a dependency or an abstraction;\n- runs the project's verification;\n- merges the integration branch's latest tip into its own branch before\n  reporting done.\n\nDone when every frontier ticket has an implementer running or reported done\n(or blocked, with the reason).\n\n## 5. Merge as they land\n\nWhen an implementer reports done, merge its branch into the integration branch\nwith a merger subagent, resolving conflicts there, and run verification on the\nresult. After the first merge, if the repo closes work through pull requests\n(or the user wants one), open a draft PR from the integration branch that\ncloses the spec and its tickets, with a body in the pr-body skill's shape.\nOtherwise call the Skill tool with \"issue-close\" for each ticket as it lands.\nIf a merge unblocks tickets, start implementers for the new frontier. Done when\nevery ticket is merged and either linked from the draft PR or closed.\n\n## 6. Review and finish\n\nWith a draft PR, mark it ready, then call the Skill tool with \"review-pr\",\nasking for the agent review (its standards and spec passes against the whole\nspec), and fix their findings\nin a single implementer subagent. Without one, report the integration branch.\nDone when the review gate is met (or the branch is reported), CI is green, and\nevery implementer worktree is removed (`git worktree remove`).\n",{"name":5,"description":7,"allowed-tools":44,"argument-hint":45},"Read, Grep, Glob, Bash(gh issue *), Bash(gh pr create*), Bash(gh pr ready*), Bash(gh pr view*), Bash(git switch*), Bash(git branch*), Bash(git merge*), Bash(git push*), Bash(git worktree*), Bash(git status*), Bash(git log*), Bash(\u003Cshared-scripts-dir>\u002Fsub-issue-frontier.sh*)","\u003Cspec issue>","main","023b01bfb4a86fbf1e38a749f1044cce3e5da67d","skills\u002Forchestration\u002Fimplement-spec",1,"https:\u002F\u002Fgithub.com\u002Fdougborg\u002Fharness-kit","https:\u002F\u002Fgithub.com\u002Fdougborg","http:\u002F\u002Fdougborg.org","Platforms and Infrastructure Software Engineer","2026-11-13 07:43:37",{"source":8,"skillName":5,"commands":56,"prompt":66,"zipAvailable":67},[57,60,63],{"tool":58,"command":59},"npx","npx skills add dougborg\u002Fharness-kit --skill implement-spec",{"tool":61,"command":62},"bunx","bunx skills add dougborg\u002Fharness-kit --skill implement-spec",{"tool":64,"command":65},"pnpm","pnpm dlx skills add dougborg\u002Fharness-kit --skill implement-spec","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fdougborg\u002Fharness-kit\u002Fblob\u002Fmain\u002Fskills\u002Forchestration\u002Fimplement-spec\u002FSKILL.md",true,[69],{"path":70,"resourceType":71,"resourceTypeDesc":72,"sizeBytes":73,"sourceHtmlUrl":74},"agents\u002Fopenai.yaml","REFERENCE","参考文档",174,"https:\u002F\u002Fgithub.com\u002Fdougborg\u002Fharness-kit\u002Fblob\u002Fmain\u002Fskills\u002Forchestration\u002Fimplement-spec\u002Fagents\u002Fopenai.yaml",[76,95,116,149,173,190],{"skillNo":77,"name":78,"nameZh":6,"description":79,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":80,"categories":81,"keywords":87,"publishedAt":39},"01M6KX4J65S5FZKMSN5DQNPSZM","teach","Teach yourself a topic over several sessions, with lessons, references, and a record of what you've learned.","https:\u002F\u002Fgithub.com\u002Fdougborg\u002Fharness-kit\u002Fblob\u002Fmain\u002Fskills\u002Fwriting\u002Fteach\u002FSKILL.md",[82],{"categoryNo":83,"categoryName":84,"taxonomyType":85,"taxonomyTypeDesc":86},"01JBSEEDCAT000000000000039","教师与教育","PROFESSION","适用职业",[78,88,89,90,91,92,93,94],"lessons","you","with","learned","record","references","sessions",{"skillNo":96,"name":97,"nameZh":6,"description":98,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":99,"categories":100,"keywords":106,"publishedAt":39},"01M6KX4FSSG7MHF00JDT5QT0BQ","svg-logo-designer","Generate SVG logos with multiple concepts, layouts, and color variations.","https:\u002F\u002Fgithub.com\u002Fdougborg\u002Fharness-kit\u002Fblob\u002Fmain\u002Fskills\u002Fwriting\u002Fsvg-logo-designer\u002FSKILL.md",[101],{"categoryNo":102,"categoryName":103,"taxonomyType":104,"taxonomyTypeDesc":105},"01JBSEEDCAT000000000000016","图像与多媒体","SCENARIO","使用场景",[107,108,109,110,111,112,90,113,114,115],"logo","designer","svg logo designer","SVG","color","concepts","write","read","generate",{"skillNo":117,"name":118,"nameZh":6,"description":119,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":120,"categories":121,"keywords":128,"publishedAt":39},"01M6KX4BD3J9MZPPSH4MENH7FP","documentation-writer","Writes and revises human-facing documentation — READMEs, contributor and setup guides, reference pages, architecture notes, CLAUDE.md, and changelog entries. Covers picking the right document type for the question being asked, structuring for skimming, writing examples that actually run, and keeping docs from going stale. Use when creating or rewriting docs, when a README has drifted from the code, or when deciding where a piece of information belongs. For SKILL.md and agent files, use \u002Fskill-writer instead.","https:\u002F\u002Fgithub.com\u002Fdougborg\u002Fharness-kit\u002Fblob\u002Fmain\u002Fskills\u002Fwriting\u002Fdocumentation-writer\u002FSKILL.md",[122,125],{"categoryNo":123,"categoryName":124,"taxonomyType":104,"taxonomyTypeDesc":105},"01JBSEEDCAT000000000000018","写作与文案",{"categoryNo":126,"categoryName":127,"taxonomyType":85,"taxonomyTypeDesc":86},"01JBSEEDCAT000000000000036","内容创作者",[129,130,131,132,133,134,135,136,137,138,139,140,141,142,143,144,145,146,147,148],"writer","documentation writer","documentation","entries","changelog","architecture","document","files","use","question","README","notes","code","examples","pages","for","information","guides","type","writing",{"skillNo":150,"name":151,"nameZh":6,"description":152,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":153,"categories":154,"keywords":155,"publishedAt":39},"01M6KX47ZJ4ZWHDN3MY8SYAWZZ","adhd-mode","Shapes every response for a reader with ADHD: the next action first, numbered steps, progress restated each turn, tangents held back, concrete time estimates, wins made visible. Stays on for the rest of the session until the reader says \"stop adhd mode\". On Claude Code, the harness-kit:adhd output style does the same without invoking this skill.","https:\u002F\u002Fgithub.com\u002Fdougborg\u002Fharness-kit\u002Fblob\u002Fmain\u002Fskills\u002Fwriting\u002Fadhd-mode\u002FSKILL.md",[],[156,157,158,159,144,160,161,90,162,163,164,165,166,167,168,169,170,171,172,141],"adhd","mode","adhd mode","next","action","kit","output","style","progress","time","back","stop","session","reader","first","REST","harness",{"skillNo":174,"name":175,"nameZh":6,"description":176,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":177,"categories":178,"keywords":179,"publishedAt":39},"01M6KX463Z6E18EPDW873GDHKB","wait-what","That last message didn't land: re-explain it with the missing context.","https:\u002F\u002Fgithub.com\u002Fdougborg\u002Fharness-kit\u002Fblob\u002Fmain\u002Fskills\u002Fthinking\u002Fwait-what\u002FSKILL.md",[],[180,181,182,90,183,184,185,186,187,188,189],"wait","wait what","re","it","missing","message","context","explain","land","last",{"skillNo":191,"name":192,"nameZh":6,"description":193,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":194,"categories":195,"keywords":196,"publishedAt":39},"01M6KX43NE1NB0Y2HECY515730","to-questionnaire","Turn a decision you can't make alone into a questionnaire for the one person who can answer it, filled in async or together in a meeting.","https:\u002F\u002Fgithub.com\u002Fdougborg\u002Fharness-kit\u002Fblob\u002Fmain\u002Fskills\u002Fthinking\u002Fto-questionnaire\u002FSKILL.md",[],[197,198,144,199,200,201,202,89,203,183,204,205],"to questionnaire","questionnaire","person","can","answer","meeting","make","async","decision"]