[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M79SEW9SFQ2AF5255M2S0PV0":3,"skill-same:01M79SEW9SFQ2AF5255M2S0PV0":51},{"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":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":25,"commitSha":26,"skillDirectory":27,"forksCount":14,"repositoryHtmlUrl":28,"repositoryHomepageUrl":6,"ownerHtmlUrl":29,"ownerBlogUrl":30,"ownerDescription":6,"updatedAt":31,"install":32,"resources":44},"01M79SEW9SFQ2AF5255M2S0PV0","to-tickets",null,"Break a plan, spec, or the current conversation into tracer-bullet tickets grouped into the fewest PRs, each ticket with its blocking edges and first red test, saved as one local file per ticket.","davner\u002Fdotfiles","davner","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F46757810?v=4","01M79SCEJR5ZY0VZD2HJ9HCCXC","Dan Avner","01M79SCEKB7MRS52247SX36BWM",0,"MIT","https:\u002F\u002Fgithub.com\u002Fdavner\u002Fdotfiles\u002Fblob\u002Fmain\u002Fhome\u002F.claude\u002Fskills\u002Fto-tickets\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: to-tickets\ndescription: Break a plan, spec, or the current conversation into tracer-bullet tickets grouped into the fewest PRs, each ticket with its blocking edges and first red test, saved as one local file per ticket.\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\nRead the tracker file, which also gives the triage label vocabulary. If there is none, tell the user to run `\u002Fsetup-dan-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, including a new file several parallel tickets would each add to (a test file, a fixture): one first ticket creates it with a marked section per ticket\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\nGive each ticket its **First red test**: the one test that must fail before the ticket's code exists, named by behaviour at a seam the spec agreed. A ticket that changes no behaviour (a pure rename, docs) says `none` and names the existing check that must stay green instead.\n\nWrite each acceptance criterion as an observable result: a behaviour, a passing check, a file that exists. Anything about commit messages or report wording stays out, since the user's commit rules govern those.\n\nGive the shared overview docs (architecture, overview, known gaps, status lines) to one closing docs ticket blocked by the rest. Each other ticket updates only the docs of the modules it changes and lists in its report what the overview docs should now say, so parallel tickets don't collide in the same file.\n\nWhen two tickets can run in parallel but touch one module, each leaves that module's shared parts alone, and a **join** ticket blocked by both does the cleanup the pair leaves (the code one removes that the other still uses, the test lists that name both). Say in each of the pair which parts the other owns.\n\nGroup the tickets into **PRs**. Tickets are the agent's work plan; a PR is what the user reviews, files and merges, and every extra PR is one more for the user to manage. Use the fewest PRs a reviewer can still follow: one PR unless a split is forced (a part must ship first, or the diff would be too large to review). Tickets in one PR land in dependency order on one branch.\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, leading with the PR count and what each PR delivers. Then list the tickets, numbered, and for each show:\n\n- **Title**: short descriptive name\n- **PR**: which PR it lands in\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- **First red test**: the failing test it starts from, or `none` and the check it keeps green\n\nAsk the user:\n\n- Does the granularity feel right? (too coarse \u002F too fine)\n- Can any PRs be combined?\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. Save the tickets\n\nSave the approved tickets the way the tracker file's \"publish to the issue tracker\" section describes.\n\n- Write one file per ticket under `\u003Cspecs folder>\u002F\u003Cfeature-slug>\u002Fissues\u002F\u003CNN>-\u003Cslug>.md`, numbered from `01` in dependency order (blockers first), using the per-ticket file template below: one ticket per file, never a single combined file. Each file's \"Blocked by\" lists the numbers and titles it depends on.\n- Then do the rest of that section: it says what is filed now, if anything, and what to tell the user. Every ticket filed or handed over is one per PR, in the issue-template shape.\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**PR:** the PR this ticket lands in, by number and one-line theme.\n\n**First red test:** the behaviour the first failing test pins, or `none` plus the check that must stay green.\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\nOne per PR, filed or handed over when the tracker file's \"publish to the issue tracker\" section says.\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 PR 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 PR's ticket that must merge first, 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\n## When headless:\n\nWhen the conversation has said the run is headless, nobody will answer step 4. With no tracker file, use the layout autopilot's Start names (`~\u002F.claude\u002Fskills\u002Fautopilot\u002FSKILL.md`). Put its four questions to yourself, settle each by the confidence rule in `grilling`'s \"When headless:\" section (`~\u002F.claude\u002Fskills\u002Fgrilling\u002FSKILL.md`), and approve the breakdown yourself. Log the breakdown and each answer to the decision log that section names. A parked question stops the run before step 5.\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\nRead the tracker file, which also gives the triage label vocabulary. If there is none, tell the user to run `\u002Fsetup-dan-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, including a new file several parallel tickets would each add to (a test file, a fixture): one first ticket creates it with a marked section per ticket\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\nGive each ticket its **First red test**: the one test that must fail before the ticket's code exists, named by behaviour at a seam the spec agreed. A ticket that changes no behaviour (a pure rename, docs) says `none` and names the existing check that must stay green instead.\n\nWrite each acceptance criterion as an observable result: a behaviour, a passing check, a file that exists. Anything about commit messages or report wording stays out, since the user's commit rules govern those.\n\nGive the shared overview docs (architecture, overview, known gaps, status lines) to one closing docs ticket blocked by the rest. Each other ticket updates only the docs of the modules it changes and lists in its report what the overview docs should now say, so parallel tickets don't collide in the same file.\n\nWhen two tickets can run in parallel but touch one module, each leaves that module's shared parts alone, and a **join** ticket blocked by both does the cleanup the pair leaves (the code one removes that the other still uses, the test lists that name both). Say in each of the pair which parts the other owns.\n\nGroup the tickets into **PRs**. Tickets are the agent's work plan; a PR is what the user reviews, files and merges, and every extra PR is one more for the user to manage. Use the fewest PRs a reviewer can still follow: one PR unless a split is forced (a part must ship first, or the diff would be too large to review). Tickets in one PR land in dependency order on one branch.\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, leading with the PR count and what each PR delivers. Then list the tickets, numbered, and for each show:\n\n- **Title**: short descriptive name\n- **PR**: which PR it lands in\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- **First red test**: the failing test it starts from, or `none` and the check it keeps green\n\nAsk the user:\n\n- Does the granularity feel right? (too coarse \u002F too fine)\n- Can any PRs be combined?\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. Save the tickets\n\nSave the approved tickets the way the tracker file's \"publish to the issue tracker\" section describes.\n\n- Write one file per ticket under `\u003Cspecs folder>\u002F\u003Cfeature-slug>\u002Fissues\u002F\u003CNN>-\u003Cslug>.md`, numbered from `01` in dependency order (blockers first), using the per-ticket file template below: one ticket per file, never a single combined file. Each file's \"Blocked by\" lists the numbers and titles it depends on.\n- Then do the rest of that section: it says what is filed now, if anything, and what to tell the user. Every ticket filed or handed over is one per PR, in the issue-template shape.\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**PR:** the PR this ticket lands in, by number and one-line theme.\n\n**First red test:** the behaviour the first failing test pins, or `none` plus the check that must stay green.\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\nOne per PR, filed or handed over when the tracker file's \"publish to the issue tracker\" section says.\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 PR 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 PR's ticket that must merge first, 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\n## When headless:\n\nWhen the conversation has said the run is headless, nobody will answer step 4. With no tracker file, use the layout autopilot's Start names (`~\u002F.claude\u002Fskills\u002Fautopilot\u002FSKILL.md`). Put its four questions to yourself, settle each by the confidence rule in `grilling`'s \"When headless:\" section (`~\u002F.claude\u002Fskills\u002Fgrilling\u002FSKILL.md`), and approve the breakdown yourself. Log the breakdown and each answer to the decision log that section names. A parked question stops the run before step 5.\n",{"name":5,"description":7,"disable-model-invocation":24},true,"main","cc6fb63be1c29cd25ac0547448353eee62f19464","home\u002F.claude\u002Fskills\u002Fto-tickets","https:\u002F\u002Fgithub.com\u002Fdavner\u002Fdotfiles","https:\u002F\u002Fgithub.com\u002Fdavner","www.danavner.com","2026-11-14 18:56:59",{"source":8,"skillName":5,"commands":33,"prompt":43,"zipAvailable":24},[34,37,40],{"tool":35,"command":36},"npx","npx skills add davner\u002Fdotfiles --skill to-tickets",{"tool":38,"command":39},"bunx","bunx skills add davner\u002Fdotfiles --skill to-tickets",{"tool":41,"command":42},"pnpm","pnpm dlx skills add davner\u002Fdotfiles --skill to-tickets","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fdavner\u002Fdotfiles\u002Fblob\u002Fmain\u002Fhome\u002F.claude\u002Fskills\u002Fto-tickets\u002FSKILL.md",[45],{"path":46,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":49,"sourceHtmlUrl":50},"agents\u002Fopenai.yaml","REFERENCE","参考文档",146,"https:\u002F\u002Fgithub.com\u002Fdavner\u002Fdotfiles\u002Fblob\u002Fmain\u002Fhome\u002F.claude\u002Fskills\u002Fto-tickets\u002Fagents\u002Fopenai.yaml",[52,59,66,73,80,87],{"skillNo":53,"name":54,"nameZh":6,"description":55,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":56,"categories":57,"keywords":58,"publishedAt":19},"01M7DZZNP2P15106XMWHD3CECC","autopilot","Run the new-work flow, idea or board item to reviewed code, with nobody watching.","https:\u002F\u002Fgithub.com\u002Fdavner\u002Fdotfiles\u002Fblob\u002Fmain\u002Fhome\u002F.claude\u002Fskills\u002Fautopilot\u002FSKILL.md",[],[],{"skillNo":60,"name":61,"nameZh":6,"description":62,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":63,"categories":64,"keywords":65,"publishedAt":19},"01M79SEZ2QHSN3YHPP1833ZPPT","writing-for-agents","Writing documents for agents. Use when creating or editing skills, or modifying AGENTS.md or CLAUDE.md.","https:\u002F\u002Fgithub.com\u002Fdavner\u002Fdotfiles\u002Fblob\u002Fmain\u002Fhome\u002F.claude\u002Fskills\u002Fwriting-for-agents\u002FSKILL.md",[],[],{"skillNo":67,"name":68,"nameZh":6,"description":69,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":70,"categories":71,"keywords":72,"publishedAt":19},"01M79SET6W048SZACE3Z3JE0QK","to-spec","Turn the current conversation into a spec saved locally as the reference the agents build from: no interview, just synthesis of what you've already discussed.","https:\u002F\u002Fgithub.com\u002Fdavner\u002Fdotfiles\u002Fblob\u002Fmain\u002Fhome\u002F.claude\u002Fskills\u002Fto-spec\u002FSKILL.md",[],[],{"skillNo":74,"name":75,"nameZh":6,"description":76,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":77,"categories":78,"keywords":79,"publishedAt":19},"01M79SEQTSNJFS3HSCV44FKT9X","teach","Teach the user a new skill or concept, within this workspace.","https:\u002F\u002Fgithub.com\u002Fdavner\u002Fdotfiles\u002Fblob\u002Fmain\u002Fhome\u002F.claude\u002Fskills\u002Fteach\u002FSKILL.md",[],[],{"skillNo":81,"name":82,"nameZh":6,"description":83,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":84,"categories":85,"keywords":86,"publishedAt":19},"01M79SENJJCBBA37FAHQKZZTS4","tdd","Test-driven development. Use when the user wants to build features or fix bugs test-first, mentions \"red-green-refactor\", or wants integration tests.","https:\u002F\u002Fgithub.com\u002Fdavner\u002Fdotfiles\u002Fblob\u002Fmain\u002Fhome\u002F.claude\u002Fskills\u002Ftdd\u002FSKILL.md",[],[],{"skillNo":88,"name":89,"nameZh":6,"description":90,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":91,"categories":92,"keywords":93,"publishedAt":19},"01M79SEEVVSVFC7SHYT3MT7J4W","tailwind-v4","Tailwind CSS v4 utility lookup, CSS-first theming, and version guardrails. Use whenever a project depends on tailwindcss v4, imports `tailwindcss` from CSS, or has an `@theme`, `@utility`, `@apply`, or `@custom-variant` rule - and for any CSS or class-name work in such a project, including writing markup with utility classes, editing a stylesheet, theming, dark mode, responsive or container queries, and build setup with Vite, PostCSS, or the CLI. Load this even for requests that look trivial, such as adding one class or changing one color, because v4 replaced the JavaScript config with CSS, renamed or removed a large part of the v3 class surface, and silently generates nothing for v3 syntax rather than failing, which makes recalled knowledge of \"Tailwind\" wrong in ways no build error reports.","https:\u002F\u002Fgithub.com\u002Fdavner\u002Fdotfiles\u002Fblob\u002Fmain\u002Fhome\u002F.claude\u002Fskills\u002Ftailwind-v4\u002FSKILL.md",[],[]]