[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6BV8ASK431W1XKWFVXZECM3":3,"skill-same:01M6BV8ASK431W1XKWFVXZECM3":71},{"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":34,"linkOnly":35,"markdownContent":36,"markdownBody":37,"frontMatter":38,"refName":40,"commitSha":41,"skillDirectory":42,"forksCount":14,"repositoryHtmlUrl":43,"repositoryHomepageUrl":6,"ownerHtmlUrl":44,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":45,"install":46,"resources":58},"01M6BV8ASK431W1XKWFVXZECM3","to-tickets",null,"Break a plan, spec, or the current conversation into a set of tracer-bullet tickets, each declaring its blocking edges, published to the configured tracker (edges as text in one file per ticket locally, or native blocking links on a real tracker).","bnferguson\u002Fdotfiles","bnferguson","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F47749?v=4","01M6BV4H2TJKK8P14W86V1ZCPP","Brandon Ferguson","01M6BV4H7GJWTZJ1BVHQ1TX11Y",0,"MIT","https:\u002F\u002Fgithub.com\u002Fbnferguson\u002Fdotfiles\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fto-tickets\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32,33],"to tickets","tickets","spec","file","SET","plan","text","tracker","conversation","as","ticket","native","links","true","break","2026-11-10 10:12:30",false,"---\nname: to-tickets\ndescription: Break a plan, spec, or the current conversation into a set of tracer-bullet tickets, each declaring its blocking edges, 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**: tracer-bullet vertical slices, each declaring the tickets that **block** it.\n\nThe issue tracker and triage label vocabulary should have been provided to you. If not, tell the user to run `\u002Fsetup-matt-pocock-skills`.\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. Explore the codebase (optional)\n\nIf you have not already explored the codebase, do so to understand the current state of the code. Ticket titles and descriptions should use the project's domain glossary vocabulary, and respect ADRs in the area you're touching.\n\nLook for opportunities to prefactor the code to make the implementation easier. \"Make the change easy, then make the easy change.\"\n\n### 3. Draft vertical slices\n\nBreak the work into **tracer bullet** tickets.\n\n\u003Cvertical-slice-rules>\n\n- Each slice cuts a narrow but COMPLETE path through every layer (schema, API, UI, tests): vertical, NOT a horizontal slice of one layer\n- A completed slice is demoable or verifiable on its own\n- Each slice is sized to fit in a single fresh context window\n- Any prefactoring should be done first\n\n\u003C\u002Fvertical-slice-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\n**Wide refactors are the exception to vertical slicing.** A **wide refactor** is one mechanical change (rename a column, retype a shared symbol) whose **blast radius** fans across the whole codebase, so a single edit breaks thousands of call sites at once and no vertical slice can land green. Don't force it into a tracer bullet; sequence it as **expand–contract**. First expand: add the new form beside the old so nothing breaks. Then migrate the call sites over in batches sized by blast radius (per package, per directory), each batch its own ticket blocked by the expand, keeping CI green batch to batch because the old form still exists. Finally contract: delete the old form once no caller remains, in a ticket blocked by every migrate batch. When even the batches can't stay green alone, keep the sequence but let them share an integration branch that all block a final integrate-and-verify ticket; green is promised only there.\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 end-to-end behaviour this ticket makes work\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 `\u002Fsetup-matt-pocock-skills` 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 \u002F sub-issue relationship where it has one; otherwise set each ticket's \"Blocked by\" to the blocking issues. 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 build:** the end-to-end behaviour this ticket makes work, from the user's perspective, not a layer-by-layer implementation list.\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 build\n\nThe end-to-end behaviour this ticket makes work, from the user's perspective, not layer-by-layer implementation.\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)\".\n\n\u003C\u002Fissue-template>\n\nIn either form, avoid specific file paths or code snippets: they go stale fast. Exception: if a prototype produced a snippet that encodes a decision more precisely than prose can (state machine, reducer, schema, type shape), inline it and note briefly that it came from a prototype. Trim to the decision-rich parts, not a working demo, just the important bits.\n","# To Tickets\n\nBreak a plan, spec, or conversation into a set of **tickets**: tracer-bullet vertical slices, each declaring the tickets that **block** it.\n\nThe issue tracker and triage label vocabulary should have been provided to you. If not, tell the user to run `\u002Fsetup-matt-pocock-skills`.\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. Explore the codebase (optional)\n\nIf you have not already explored the codebase, do so to understand the current state of the code. Ticket titles and descriptions should use the project's domain glossary vocabulary, and respect ADRs in the area you're touching.\n\nLook for opportunities to prefactor the code to make the implementation easier. \"Make the change easy, then make the easy change.\"\n\n### 3. Draft vertical slices\n\nBreak the work into **tracer bullet** tickets.\n\n\u003Cvertical-slice-rules>\n\n- Each slice cuts a narrow but COMPLETE path through every layer (schema, API, UI, tests): vertical, NOT a horizontal slice of one layer\n- A completed slice is demoable or verifiable on its own\n- Each slice is sized to fit in a single fresh context window\n- Any prefactoring should be done first\n\n\u003C\u002Fvertical-slice-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\n**Wide refactors are the exception to vertical slicing.** A **wide refactor** is one mechanical change (rename a column, retype a shared symbol) whose **blast radius** fans across the whole codebase, so a single edit breaks thousands of call sites at once and no vertical slice can land green. Don't force it into a tracer bullet; sequence it as **expand–contract**. First expand: add the new form beside the old so nothing breaks. Then migrate the call sites over in batches sized by blast radius (per package, per directory), each batch its own ticket blocked by the expand, keeping CI green batch to batch because the old form still exists. Finally contract: delete the old form once no caller remains, in a ticket blocked by every migrate batch. When even the batches can't stay green alone, keep the sequence but let them share an integration branch that all block a final integrate-and-verify ticket; green is promised only there.\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 end-to-end behaviour this ticket makes work\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 `\u002Fsetup-matt-pocock-skills` 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 \u002F sub-issue relationship where it has one; otherwise set each ticket's \"Blocked by\" to the blocking issues. 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 build:** the end-to-end behaviour this ticket makes work, from the user's perspective, not a layer-by-layer implementation list.\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 build\n\nThe end-to-end behaviour this ticket makes work, from the user's perspective, not layer-by-layer implementation.\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)\".\n\n\u003C\u002Fissue-template>\n\nIn either form, avoid specific file paths or code snippets: they go stale fast. Exception: if a prototype produced a snippet that encodes a decision more precisely than prose can (state machine, reducer, schema, type shape), inline it and note briefly that it came from a prototype. Trim to the decision-rich parts, not a working demo, just the important bits.\n",{"name":5,"description":7,"disable-model-invocation":39},true,"main","e63965e4644984470d4cc8b3014a8b001f0c2666",".agents\u002Fskills\u002Fto-tickets","https:\u002F\u002Fgithub.com\u002Fbnferguson\u002Fdotfiles","https:\u002F\u002Fgithub.com\u002Fbnferguson","2026-11-11 03:04:59",{"source":8,"skillName":5,"commands":47,"prompt":57,"zipAvailable":39},[48,51,54],{"tool":49,"command":50},"npx","npx skills add bnferguson\u002Fdotfiles --skill to-tickets",{"tool":52,"command":53},"bunx","bunx skills add bnferguson\u002Fdotfiles --skill to-tickets",{"tool":55,"command":56},"pnpm","pnpm dlx skills add bnferguson\u002Fdotfiles --skill to-tickets","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fbnferguson\u002Fdotfiles\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fto-tickets\u002FSKILL.md",[59,65],{"path":60,"resourceType":61,"resourceTypeDesc":62,"sizeBytes":63,"sourceHtmlUrl":64},"agents\u002Fopenai.yaml","REFERENCE","参考文档",146,"https:\u002F\u002Fgithub.com\u002Fbnferguson\u002Fdotfiles\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fto-tickets\u002Fagents\u002Fopenai.yaml",{"path":66,"resourceType":67,"resourceTypeDesc":68,"sizeBytes":69,"sourceHtmlUrl":70},"assets\u002Fchecklist.md","ASSET","资产文件",81,"https:\u002F\u002Fgithub.com\u002Fawebai\u002Faweb\u002Fblob\u002Fmain\u002Fnaapp\u002Flibrary\u002Ftests\u002Fvectors\u002Fblueprints\u002Fengineering\u002Fexpected\u002Fmaterialized-home\u002Fdeveloper\u002Fskills\u002Fimplement\u002Fassets\u002Fchecklist.md",[72,105,122,153,162,175],{"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":76,"licenseFileUrl":77,"sourceHtmlUrl":78,"categories":79,"keywords":85,"publishedAt":34},"01M6BVA3RS3M016FANZ6792F9H","skill-creator","Guide for creating effective skills. This skill should be used when users want to create a new skill (or update an existing skill) that extends Claude's capabilities with specialized knowledge, workflows, or tool integrations.","Apache-2.0","https:\u002F\u002Fgithub.com\u002Fbnferguson\u002Fdotfiles\u002Fblob\u002Fmain\u002Fclaude\u002Fconfig\u002Fskills\u002Fskill-creator\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fbnferguson\u002Fdotfiles\u002Fblob\u002Fmain\u002Fclaude\u002Fconfig\u002Fskills\u002Fskill-creator\u002FSKILL.md",[80],{"categoryNo":81,"categoryName":82,"taxonomyType":83,"taxonomyTypeDesc":84},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[86,87,88,89,90,91,92,93,94,95,96,97,98,99,100,101,102,103,104],"creator","skill creator","specialized","workflows","create","update","capabilities","knowledge","tool","integrations","guide","new skill","existing skill","users","with","for","Existing","when","new",{"skillNo":106,"name":107,"nameZh":6,"description":108,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":109,"categories":110,"keywords":119,"publishedAt":34},"01M6BV94WN2RPYM8N6PN8TBNT8","writing-shape","Writing, exploit: shape raw material into an article, paragraph by paragraph.","https:\u002F\u002Fgithub.com\u002Fbnferguson\u002Fdotfiles\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fwriting-shape\u002FSKILL.md",[111,114],{"categoryNo":112,"categoryName":113,"taxonomyType":83,"taxonomyTypeDesc":84},"01JBSEEDCAT000000000000018","写作与文案",{"categoryNo":115,"categoryName":116,"taxonomyType":117,"taxonomyTypeDesc":118},"01JBSEEDCAT000000000000036","内容创作者","PROFESSION","适用职业",[120,121],"writing shape","writing",{"skillNo":123,"name":124,"nameZh":6,"description":125,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":76,"licenseFileUrl":126,"sourceHtmlUrl":127,"categories":128,"keywords":135,"publishedAt":34},"01M6BV8QDFJ6PXBVK5NFBZT5M7","webapp-testing","Test local web applications using Playwright. Use when verifying frontend functionality, debugging UI behavior, capturing browser screenshots, or viewing browser logs.","https:\u002F\u002Fgithub.com\u002Fbnferguson\u002Fdotfiles\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fwebapp-testing\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fbnferguson\u002Fdotfiles\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fwebapp-testing\u002FSKILL.md",[129,132],{"categoryNo":130,"categoryName":131,"taxonomyType":83,"taxonomyTypeDesc":84},"01JBSEEDCAT000000000000008","测试与质量",{"categoryNo":133,"categoryName":134,"taxonomyType":83,"taxonomyTypeDesc":84},"01JBSEEDCAT000000000000009","前端开发",[136,137,138,139,140,141,142,143,144,145,146,147,148,149,150,151,152,103],"webapp","webapp testing","testing","browser","frontend","screenshots","playwright","test","web","debugging","ui","logs","applications","behavior","use","local","test local",{"skillNo":154,"name":155,"nameZh":6,"description":156,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":157,"categories":158,"keywords":159,"publishedAt":34},"01M6BV8MDXKXNVHKS3QF3YDFTF","wait-what","Stop. That last message did not land: re-pitch it.","https:\u002F\u002Fgithub.com\u002Fbnferguson\u002Fdotfiles\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fwait-what\u002FSKILL.md",[],[160,161],"wait what","land",{"skillNo":163,"name":164,"nameZh":6,"description":165,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":166,"categories":167,"keywords":171,"publishedAt":34},"01M6BV756DJHT5BDA1HVRVHJJ7","prototype","Build a throwaway prototype to answer a design question. Use when the user wants to sanity-check whether a state model or logic feels right, or explore what a UI should look like.","https:\u002F\u002Fgithub.com\u002Fbnferguson\u002Fdotfiles\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fprototype\u002FSKILL.md",[168],{"categoryNo":169,"categoryName":170,"taxonomyType":117,"taxonomyTypeDesc":118},"01JBSEEDCAT000000000000032","设计师",[164,172,173,146,174],"design","explore","state",{"skillNo":176,"name":177,"nameZh":6,"description":178,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":179,"categories":180,"keywords":182,"publishedAt":34},"01M6BV6SBW166685KVBPWM2K4N","improve-codebase-architecture","Scan a codebase for deepening opportunities, present them as a visual HTML report, then grill through whichever one you pick.","https:\u002F\u002Fgithub.com\u002Fbnferguson\u002Fdotfiles\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fimprove-codebase-architecture\u002FSKILL.md",[181],{"categoryNo":133,"categoryName":134,"taxonomyType":83,"taxonomyTypeDesc":84},[183,184,185,186],"architecture","improve","improve codebase architecture","report"]