[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7FATR0E1WW92C4RDB7MRC18":3,"skill-same:01M7FATR0E1WW92C4RDB7MRC18":43},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"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":13,"repositoryHtmlUrl":27,"repositoryHomepageUrl":6,"ownerHtmlUrl":28,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":29,"install":30,"resources":42},"01M7FATR0E1WW92C4RDB7MRC18","mpc_implement-spec",null,"Make the results of a whole spec from \u002Fboarlabs:mpc_to-spec and \u002Fboarlabs:mpc_to-tickets: every ticket's result on its platform, each one checked by \u002Fboarlabs:boar_review.","boarlabsxyz\u002Fskills","boarlabsxyz","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F183485413?v=4","01M7FAAY4JD8XATY5VPC07M8PA","01M7FAAY574ZFBK3KWT1V57ETE",0,"MIT","https:\u002F\u002Fgithub.com\u002Fboarlabsxyz\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fmpc_implement-spec\u002FSKILL.md",[],[],"2026-11-16 10:05:34",false,"---\nname: mpc_implement-spec\ndescription: \"Make the results of a whole spec from \u002Fboarlabs:mpc_to-spec and \u002Fboarlabs:mpc_to-tickets: every ticket's result on its platform, each one checked by \u002Fboarlabs:boar_review.\"\ndisable-model-invocation: true\n---\n\nYou have been provided a spec. This spec should have tickets associated with it, describing what to make.\n\nThe issue tracker should have been provided to you. If not, tell the user to run `\u002Fboarlabs:boar_setup`.\n\nThe goal is every ticket's **result** made on the platform its ticket names (a Google Doc or Drive file, a ClickUp task or doc, a Miro board, a Claude artifact), checked, and every ticket resolved the way the issue tracker closes work. Results never go into git: there is no integration branch, no worktree and no pull request.\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 results already made. Don't duplicate information already available via pointers.\n\n**Maker 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. Every ticket must carry a **Result** section (platform, place with a link, name) and a **Marketing** line (`yes` or `no`). If one lacks either, stop and ask the user; there is no default.\n\n2. (optional) When the tickets need exploration (a question about the web or about the repository's context), call the Skill tool with `boar_codex` and start a research run with a precise question and a criterion of done. Read its evidence before relying on it. Save what it found as notes the maker subagents can point at.\n\n3. Use **maker subagents** to make each ticket on the frontier, one subagent per ticket. Each maker subagent:\n   - reads its ticket, the spec and the notes it is pointed at;\n   - makes the result on the ticket's platform, in the ticket's place, under the ticket's name, through the session's connectors;\n   - with `Marketing: yes`, uses the `chs_*` skills that fit the result, picked by their descriptions; with `Marketing: no`, uses none of them;\n   - reports the result's link, and nothing else changed.\n\n4. Check each finished result **one at a time, in this session**: call the Skill tool with `boar_review` for the ticket. Playwright drives one browser, so two checks never run at once. Meet its findings on the platform, as `boar_review` says.\n\n5. Close each checked ticket the way the issue tracker closes work, with a comment that links the result and carries the `boar_review` report.\n\n6. If this changes the **frontier** of available tickets, kick off more **maker subagents** for the new tickets. This allows for maximum concurrency.\n\n7. Commit and push what this run wrote to the repository (notes, glossary or ADR changes), as described below. Report every ticket with its result's link.\n\n## Committing\n\nResults live on their platforms and are never committed. What this run wrote to the repository itself is context: commit only those paths (`git add \u003Cpaths>`, never `git add .`) on `main` with a short message naming the spec, then `git push`. If the push is refused, stop and tell the user why; never force it.\n","You have been provided a spec. This spec should have tickets associated with it, describing what to make.\n\nThe issue tracker should have been provided to you. If not, tell the user to run `\u002Fboarlabs:boar_setup`.\n\nThe goal is every ticket's **result** made on the platform its ticket names (a Google Doc or Drive file, a ClickUp task or doc, a Miro board, a Claude artifact), checked, and every ticket resolved the way the issue tracker closes work. Results never go into git: there is no integration branch, no worktree and no pull request.\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 results already made. Don't duplicate information already available via pointers.\n\n**Maker 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. Every ticket must carry a **Result** section (platform, place with a link, name) and a **Marketing** line (`yes` or `no`). If one lacks either, stop and ask the user; there is no default.\n\n2. (optional) When the tickets need exploration (a question about the web or about the repository's context), call the Skill tool with `boar_codex` and start a research run with a precise question and a criterion of done. Read its evidence before relying on it. Save what it found as notes the maker subagents can point at.\n\n3. Use **maker subagents** to make each ticket on the frontier, one subagent per ticket. Each maker subagent:\n   - reads its ticket, the spec and the notes it is pointed at;\n   - makes the result on the ticket's platform, in the ticket's place, under the ticket's name, through the session's connectors;\n   - with `Marketing: yes`, uses the `chs_*` skills that fit the result, picked by their descriptions; with `Marketing: no`, uses none of them;\n   - reports the result's link, and nothing else changed.\n\n4. Check each finished result **one at a time, in this session**: call the Skill tool with `boar_review` for the ticket. Playwright drives one browser, so two checks never run at once. Meet its findings on the platform, as `boar_review` says.\n\n5. Close each checked ticket the way the issue tracker closes work, with a comment that links the result and carries the `boar_review` report.\n\n6. If this changes the **frontier** of available tickets, kick off more **maker subagents** for the new tickets. This allows for maximum concurrency.\n\n7. Commit and push what this run wrote to the repository (notes, glossary or ADR changes), as described below. Report every ticket with its result's link.\n\n## Committing\n\nResults live on their platforms and are never committed. What this run wrote to the repository itself is context: commit only those paths (`git add \u003Cpaths>`, never `git add .`) on `main` with a short message naming the spec, then `git push`. If the push is refused, stop and tell the user why; never force it.\n",{"name":5,"description":7,"disable-model-invocation":23},true,"main","70822f79cdb0fbf902c74433bbb4a7bc4ac033cc","skills\u002Fmpc_implement-spec","https:\u002F\u002Fgithub.com\u002Fboarlabsxyz\u002Fskills","https:\u002F\u002Fgithub.com\u002Fboarlabsxyz","2026-10-21 20:41:04",{"source":8,"skillName":5,"commands":31,"prompt":41,"zipAvailable":23},[32,35,38],{"tool":33,"command":34},"npx","npx skills add boarlabsxyz\u002Fskills --skill mpc_implement-spec",{"tool":36,"command":37},"bunx","bunx skills add boarlabsxyz\u002Fskills --skill mpc_implement-spec",{"tool":39,"command":40},"pnpm","pnpm dlx skills add boarlabsxyz\u002Fskills --skill mpc_implement-spec","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fboarlabsxyz\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fmpc_implement-spec\u002FSKILL.md",[],[44,51,58,65,72,79],{"skillNo":45,"name":46,"nameZh":6,"description":47,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":48,"categories":49,"keywords":50,"publishedAt":18},"01M7FAW878DNGW855BTMPHJGGT","mpc_writing-shape","Writing, exploit: shape raw material into an article, paragraph by paragraph.","https:\u002F\u002Fgithub.com\u002Fboarlabsxyz\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fmpc_writing-shape\u002FSKILL.md",[],[],{"skillNo":52,"name":53,"nameZh":6,"description":54,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":55,"categories":56,"keywords":57,"publishedAt":18},"01M7FAW53VT22GATJ9VNEQ21HY","mpc_writing-fragments","Writing, explore: mine raw fragments, no structure yet.","https:\u002F\u002Fgithub.com\u002Fboarlabsxyz\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fmpc_writing-fragments\u002FSKILL.md",[],[],{"skillNo":59,"name":60,"nameZh":6,"description":61,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":62,"categories":63,"keywords":64,"publishedAt":18},"01M7FAW2E42FBEKVX4RH82RZ55","mpc_writing-for-agents","Writing documents for agents. Use when creating or editing skills, or modifying AGENTS.md or CLAUDE.md.","https:\u002F\u002Fgithub.com\u002Fboarlabsxyz\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fmpc_writing-for-agents\u002FSKILL.md",[],[],{"skillNo":66,"name":67,"nameZh":6,"description":68,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":69,"categories":70,"keywords":71,"publishedAt":18},"01M7FAVZ8S0KT45XMZPWMA2KCS","mpc_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\u002Fboarlabsxyz\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fmpc_writing-beats\u002FSKILL.md",[],[],{"skillNo":73,"name":74,"nameZh":6,"description":75,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":76,"categories":77,"keywords":78,"publishedAt":18},"01M7FAVV4EQBCDJA10KAHRKFSQ","mpc_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\u002Fboarlabsxyz\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fmpc_wayfinder\u002FSKILL.md",[],[],{"skillNo":80,"name":81,"nameZh":6,"description":82,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":83,"categories":84,"keywords":85,"publishedAt":18},"01M7FAVR30JXV3830GWCJSVJZP","mpc_wait-what","Stop. That last message did not land: re-pitch it.","https:\u002F\u002Fgithub.com\u002Fboarlabsxyz\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fmpc_wait-what\u002FSKILL.md",[],[]]