[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7FAVFX3SFF0DHPSDB6S14GG":3,"skill-same:01M7FAVFX3SFF0DHPSDB6S14GG":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},"01M7FAVFX3SFF0DHPSDB6S14GG","mpc_to-tickets",null,"Break a plan, spec, or the current conversation into a set of tickets, each declaring its blocking edges, its Result and its Marketing line, published to the configured tracker (edges as text in one file per ticket locally, or native blocking links on a real tracker).","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_to-tickets\u002FSKILL.md",[],[],"2026-11-16 10:05:34",false,"---\nname: mpc_to-tickets\ndescription: Break a plan, spec, or the current conversation into a set of tickets, each declaring its blocking edges, its Result and its Marketing line, published to the configured tracker (edges as text in one file per ticket locally, or native blocking links on a real tracker).\ndisable-model-invocation: true\n---\n\n# To Tickets\n\nBreak a plan, spec, or conversation into a set of **tickets**: each one makes one **result** (or one complete part of a result) that can be checked on its own, and declares the tickets that **block** it, where its result goes, and whether it is marketing work.\n\nThe issue tracker and triage label vocabulary should have been provided to you. If not, tell the user to run `\u002Fboarlabs:boar_setup`.\n\n## Process\n\n### 1. Gather context\n\nWork from whatever is already in the conversation context. If the user passes a reference (a spec path, an issue number or URL) as an argument, fetch it and read its full body and comments.\n\n### 2. Read the context (optional)\n\nIf you have not already, read the repository's context: `GLOSSARY.md`, ADRs, research notes and the Q&A logs under `docs\u002Fqna\u002F`. Ticket titles and descriptions should use the project's domain glossary vocabulary, and respect ADRs in the area you're touching.\n\n### 3. Draft the tickets\n\n\u003Cticket-rules>\n\n- Each ticket makes one result, or one complete part of a result, that can be checked on its own\n- Each ticket is sized to fit in a single fresh context window\n- Research that several tickets need comes first, as its own ticket\n\n\u003C\u002Fticket-rules>\n\nGive each ticket its **blocking edges**: the other tickets that must complete before it can start. A ticket with no blockers can start immediately.\n\nGive each ticket its two required lines. There is no default for either:\n\n- **Result**: the platform (a Google Doc or Drive file, a ClickUp task or doc, a Miro board, a Claude artifact, …), the place on it (a folder, list or board, with a link) and the result's name. Only a platform the session can write to through its connectors counts.\n- **Marketing**: `yes` or `no`, taken from the spec; a ticket differs from the spec only where the spec says so. With `yes`, `\u002Fboarlabs:mpc_implement` uses the `chs_*` skills that fit; with `no`, it uses none.\n\nIf you cannot fill either line for a ticket, ask the user before publishing.\n\n### 4. Quiz the user\n\nPresent the proposed breakdown as a numbered list. For each ticket, show:\n\n- **Title**: short descriptive name\n- **Blocked by**: which other tickets (if any) must complete first\n- **What it delivers**: the result this ticket makes\n- **Result**: platform, place, name\n- **Marketing**: yes or no\n\nAsk the user:\n\n- Does the granularity feel right? (too coarse \u002F too fine)\n- Are the blocking edges correct: does each ticket only depend on tickets that genuinely gate it?\n- Should any tickets be merged or split further?\n\nIterate until the user approves the breakdown.\n\n### 5. Publish the tickets to the configured tracker\n\nPublish the approved tickets. **How** depends on the tracker `\u002Fboarlabs:boar_setup` configured; the tickets are the same either way, only the shape of the blocking edges changes:\n\n- **Local files** → write one file per ticket under `.scratch\u002F\u003Cfeature-slug>\u002Fissues\u002F\u003CNN>-\u003Cslug>.md`, numbered from `01` in dependency order (blockers first). Each file's \"Blocked by\" lists the numbers\u002Ftitles it depends on. Use the per-ticket file template below: one ticket per file, never a single combined file.\n- **A real issue tracker (GitHub, Linear, …)** → publish one issue per ticket in dependency order (blockers first) so each ticket's blocking edges can reference real identifiers. Use the platform's native blocking relationship where it has one; otherwise set each ticket's \"Blocked by\" to the blocking issues. If the source was an existing issue, make each ticket its sub-issue (tracker doc's operation). Apply the `ready-for-agent` triage label unless instructed otherwise; the tickets are agent-grabbable by construction.\n\nWork the **frontier**: any ticket whose blockers are all done. For a purely linear chain that means top to bottom.\n\nDo NOT close or modify any parent issue.\n\n\u003Clocal-ticket-template>\n\n# \u003CNN>: \u003CTicket title>\n\n**What to make:** the result this ticket makes, from the reader's perspective.\n\n**Result:** the platform, the place (with a link) and the name.\n\n**Marketing:** yes or no.\n\n**Blocked by:** the numbers\u002Ftitles of the tickets that gate this one, or \"None (can start immediately)\".\n\n**Status:** ready-for-agent\n\n- [ ] Acceptance criterion 1\n- [ ] Acceptance criterion 2\n\n\u003C\u002Flocal-ticket-template>\n\n\u003Cissue-template>\n\n## Parent\n\nA reference to the parent issue on the tracker (if the source was an existing issue, otherwise omit this section).\n\n## What to make\n\nThe result this ticket makes, from the reader's perspective.\n\n## Result\n\n- **Platform**: where the result lives\n- **Place**: the folder, list or board, with a link\n- **Name**: the result's name\n\n## Marketing\n\nyes or no\n\n## Acceptance criteria\n\n- [ ] Criterion 1\n- [ ] Criterion 2\n\n## Blocked by\n\n- A reference to each blocking ticket, or \"None (can start immediately)\". Omit this section when blockers were set as native edges.\n\n\u003C\u002Fissue-template>\n\nIn either form, point at the spec, the Q&A log and research notes rather than copying them.\n","# To Tickets\n\nBreak a plan, spec, or conversation into a set of **tickets**: each one makes one **result** (or one complete part of a result) that can be checked on its own, and declares the tickets that **block** it, where its result goes, and whether it is marketing work.\n\nThe issue tracker and triage label vocabulary should have been provided to you. If not, tell the user to run `\u002Fboarlabs:boar_setup`.\n\n## Process\n\n### 1. Gather context\n\nWork from whatever is already in the conversation context. If the user passes a reference (a spec path, an issue number or URL) as an argument, fetch it and read its full body and comments.\n\n### 2. Read the context (optional)\n\nIf you have not already, read the repository's context: `GLOSSARY.md`, ADRs, research notes and the Q&A logs under `docs\u002Fqna\u002F`. Ticket titles and descriptions should use the project's domain glossary vocabulary, and respect ADRs in the area you're touching.\n\n### 3. Draft the tickets\n\n\u003Cticket-rules>\n\n- Each ticket makes one result, or one complete part of a result, that can be checked on its own\n- Each ticket is sized to fit in a single fresh context window\n- Research that several tickets need comes first, as its own ticket\n\n\u003C\u002Fticket-rules>\n\nGive each ticket its **blocking edges**: the other tickets that must complete before it can start. A ticket with no blockers can start immediately.\n\nGive each ticket its two required lines. There is no default for either:\n\n- **Result**: the platform (a Google Doc or Drive file, a ClickUp task or doc, a Miro board, a Claude artifact, …), the place on it (a folder, list or board, with a link) and the result's name. Only a platform the session can write to through its connectors counts.\n- **Marketing**: `yes` or `no`, taken from the spec; a ticket differs from the spec only where the spec says so. With `yes`, `\u002Fboarlabs:mpc_implement` uses the `chs_*` skills that fit; with `no`, it uses none.\n\nIf you cannot fill either line for a ticket, ask the user before publishing.\n\n### 4. Quiz the user\n\nPresent the proposed breakdown as a numbered list. For each ticket, show:\n\n- **Title**: short descriptive name\n- **Blocked by**: which other tickets (if any) must complete first\n- **What it delivers**: the result this ticket makes\n- **Result**: platform, place, name\n- **Marketing**: yes or no\n\nAsk the user:\n\n- Does the granularity feel right? (too coarse \u002F too fine)\n- Are the blocking edges correct: does each ticket only depend on tickets that genuinely gate it?\n- Should any tickets be merged or split further?\n\nIterate until the user approves the breakdown.\n\n### 5. Publish the tickets to the configured tracker\n\nPublish the approved tickets. **How** depends on the tracker `\u002Fboarlabs:boar_setup` configured; the tickets are the same either way, only the shape of the blocking edges changes:\n\n- **Local files** → write one file per ticket under `.scratch\u002F\u003Cfeature-slug>\u002Fissues\u002F\u003CNN>-\u003Cslug>.md`, numbered from `01` in dependency order (blockers first). Each file's \"Blocked by\" lists the numbers\u002Ftitles it depends on. Use the per-ticket file template below: one ticket per file, never a single combined file.\n- **A real issue tracker (GitHub, Linear, …)** → publish one issue per ticket in dependency order (blockers first) so each ticket's blocking edges can reference real identifiers. Use the platform's native blocking relationship where it has one; otherwise set each ticket's \"Blocked by\" to the blocking issues. If the source was an existing issue, make each ticket its sub-issue (tracker doc's operation). Apply the `ready-for-agent` triage label unless instructed otherwise; the tickets are agent-grabbable by construction.\n\nWork the **frontier**: any ticket whose blockers are all done. For a purely linear chain that means top to bottom.\n\nDo NOT close or modify any parent issue.\n\n\u003Clocal-ticket-template>\n\n# \u003CNN>: \u003CTicket title>\n\n**What to make:** the result this ticket makes, from the reader's perspective.\n\n**Result:** the platform, the place (with a link) and the name.\n\n**Marketing:** yes or no.\n\n**Blocked by:** the numbers\u002Ftitles of the tickets that gate this one, or \"None (can start immediately)\".\n\n**Status:** ready-for-agent\n\n- [ ] Acceptance criterion 1\n- [ ] Acceptance criterion 2\n\n\u003C\u002Flocal-ticket-template>\n\n\u003Cissue-template>\n\n## Parent\n\nA reference to the parent issue on the tracker (if the source was an existing issue, otherwise omit this section).\n\n## What to make\n\nThe result this ticket makes, from the reader's perspective.\n\n## Result\n\n- **Platform**: where the result lives\n- **Place**: the folder, list or board, with a link\n- **Name**: the result's name\n\n## Marketing\n\nyes or no\n\n## Acceptance criteria\n\n- [ ] Criterion 1\n- [ ] Criterion 2\n\n## Blocked by\n\n- A reference to each blocking ticket, or \"None (can start immediately)\". Omit this section when blockers were set as native edges.\n\n\u003C\u002Fissue-template>\n\nIn either form, point at the spec, the Q&A log and research notes rather than copying them.\n",{"name":5,"description":7,"disable-model-invocation":23},true,"main","70822f79cdb0fbf902c74433bbb4a7bc4ac033cc","skills\u002Fmpc_to-tickets","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_to-tickets",{"tool":36,"command":37},"bunx","bunx skills add boarlabsxyz\u002Fskills --skill mpc_to-tickets",{"tool":39,"command":40},"pnpm","pnpm dlx skills add boarlabsxyz\u002Fskills --skill mpc_to-tickets","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fboarlabsxyz\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fmpc_to-tickets\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",[],[]]