[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M79SPNVJQ0WNWH7PBEM5Y463":3,"skill-same:01M79SPNVJQ0WNWH7PBEM5Y463":53},{"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":26,"commitSha":27,"skillDirectory":28,"forksCount":14,"repositoryHtmlUrl":29,"repositoryHomepageUrl":6,"ownerHtmlUrl":30,"ownerBlogUrl":31,"ownerDescription":32,"updatedAt":33,"install":34,"resources":46},"01M79SPNVJQ0WNWH7PBEM5Y463","to-tickets",null,"Break a spec, plan, or conversation into tracer-bullet vertical-slice tickets with blocking edges — \"turn this into tickets\", \"break this down\", \"what's the work?\". Pairs with skill-tree:to-spec upstream and skill-tree:handoff downstream.","dannybrown37\u002Fskill-tree","dannybrown37","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F28059438?v=4","01M79SKVHAKWQH9VF0G6KQRZZ2","Danny Brown","01M79SKVJ1X8VHPTK7MKMHBRD2",0,"MIT","https:\u002F\u002Fgithub.com\u002Fdannybrown37\u002Fskill-tree\u002Fblob\u002Fmain\u002Fskills\u002Fto-tickets\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: to-tickets\ndescription: \"Break a spec, plan, or conversation into tracer-bullet vertical-slice tickets with blocking edges — \\\"turn this into tickets\\\", \\\"break this down\\\", \\\"what's the work?\\\". Pairs with skill-tree:to-spec upstream and skill-tree:handoff downstream.\"\nuser-invocable: true\ndisable-model-invocation: true\nallowed-tools: Read, Grep, Glob, Bash, Write\n---\n\n# To Tickets\n\nBreak a plan, spec, or conversation into a set of tickets: tracer-bullet vertical slices, each\ndeclaring the tickets that block it.\n\n## Process\n\n### 1. Gather context\n\nWork from whatever is already in the conversation. If the user passes a reference (a spec path,\nan issue number or URL), fetch it and read its full body and comments.\n\n### 2. Explore the codebase\n\nIf you haven't already, explore the codebase to understand current state. Ticket titles and\ndescriptions should use the project's `CONTEXT.md` vocabulary and respect ADRs in the area\nbeing touched.\n\nLook for opportunities to prefactor — \"make the change easy, then make the easy change.\"\nPrefactoring is its own ticket, blocked by nothing, blocking the work that needs it.\n\n### 3. Draft vertical slices\n\nEach slice cuts a narrow but **complete** path through every layer (schema, API, UI, tests) —\nvertical, not a horizontal slice of one layer.\n\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- Give each ticket its blocking edges: the other tickets that must complete before it can start\n\n**Greenfield or a new subsystem?** The first ticket is a **walking skeleton** (Alistair\nCockburn): the thinnest end-to-end path that runs — real wiring through every layer, built,\ndeployed or runnable, and tested, doing almost nothing. Every other slice blocks on it and\nfleshes it out. Skip it when the architecture already exists; the first slice is just a slice.\n\n**Wide refactors** are the exception. A mechanical change whose blast radius fans across the\nwhole codebase (rename a column, retype a shared symbol) can't land as a vertical slice. Use\nexpand–contract:\n\n1. **Expand**: add the new form beside the old (nothing breaks)\n2. **Migrate**: move call sites over in batches sized by blast radius, each batch its own\n   ticket, keeping CI green batch-to-batch because the old form still exists\n3. **Contract**: delete the old form once no caller remains, blocked by every migrate batch\n\n### 4. Quiz the user\n\nPresent the breakdown as a numbered list. For each ticket:\n\n- **Title**: short descriptive name\n- **Blocked by**: which other tickets must complete first (or \"None\")\n- **What it delivers**: the end-to-end behaviour this ticket makes work\n\nAsk:\n- Does the granularity feel right? (too coarse \u002F too fine)\n- Are the blocking edges correct?\n- Should any tickets be merged or split?\n\nIterate until the user approves.\n\n### 5. Publish\n\nAsk the user where tickets go. Two modes:\n\n**Local files** — one file per ticket under `docs\u002Ftickets\u002F\u003Cfeature-slug>\u002F`, numbered from `01`\nin dependency order (blockers first). Use the template in\n[references\u002Fticket-template.md](references\u002Fticket-template.md).\n\n**Issue tracker** (GitHub, Linear, etc.) — publish in dependency order so blocking edges can\nreference real identifiers. Use the platform's native blocking\u002Fsub-issue relationships where\navailable. Confirm with the user before posting — human-in-the-loop applies to anything visible\noutside the local working tree.\n\nWork the frontier: any ticket whose blockers are all done.\n\n## What goes in a ticket\n\n- **What to build**: end-to-end behaviour from the user's perspective, not layer-by-layer\n  implementation steps\n- **Acceptance criteria**: checkboxes, each verifiable\n- **Blocked by**: references to blocking tickets, or \"None (can start immediately)\"\n\nAvoid specific file paths or code snippets — they go stale. Exception: if a prototype produced\na snippet that encodes a decision more precisely than prose (state machine, schema, type shape),\ninline the decision-rich parts and note it came from a prototype.\n\n## Integration\n\n- **[[to-spec]]** produces the spec this skill consumes\n- **[[domain-modeling]]** provides the vocabulary tickets are written in\n- **[[handoff]]** picks up where this leaves off — `handoff add` items from the approved\n  ticket list to seed the backlog for a work session\n","# To Tickets\n\nBreak a plan, spec, or conversation into a set of tickets: tracer-bullet vertical slices, each\ndeclaring the tickets that block it.\n\n## Process\n\n### 1. Gather context\n\nWork from whatever is already in the conversation. If the user passes a reference (a spec path,\nan issue number or URL), fetch it and read its full body and comments.\n\n### 2. Explore the codebase\n\nIf you haven't already, explore the codebase to understand current state. Ticket titles and\ndescriptions should use the project's `CONTEXT.md` vocabulary and respect ADRs in the area\nbeing touched.\n\nLook for opportunities to prefactor — \"make the change easy, then make the easy change.\"\nPrefactoring is its own ticket, blocked by nothing, blocking the work that needs it.\n\n### 3. Draft vertical slices\n\nEach slice cuts a narrow but **complete** path through every layer (schema, API, UI, tests) —\nvertical, not a horizontal slice of one layer.\n\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- Give each ticket its blocking edges: the other tickets that must complete before it can start\n\n**Greenfield or a new subsystem?** The first ticket is a **walking skeleton** (Alistair\nCockburn): the thinnest end-to-end path that runs — real wiring through every layer, built,\ndeployed or runnable, and tested, doing almost nothing. Every other slice blocks on it and\nfleshes it out. Skip it when the architecture already exists; the first slice is just a slice.\n\n**Wide refactors** are the exception. A mechanical change whose blast radius fans across the\nwhole codebase (rename a column, retype a shared symbol) can't land as a vertical slice. Use\nexpand–contract:\n\n1. **Expand**: add the new form beside the old (nothing breaks)\n2. **Migrate**: move call sites over in batches sized by blast radius, each batch its own\n   ticket, keeping CI green batch-to-batch because the old form still exists\n3. **Contract**: delete the old form once no caller remains, blocked by every migrate batch\n\n### 4. Quiz the user\n\nPresent the breakdown as a numbered list. For each ticket:\n\n- **Title**: short descriptive name\n- **Blocked by**: which other tickets must complete first (or \"None\")\n- **What it delivers**: the end-to-end behaviour this ticket makes work\n\nAsk:\n- Does the granularity feel right? (too coarse \u002F too fine)\n- Are the blocking edges correct?\n- Should any tickets be merged or split?\n\nIterate until the user approves.\n\n### 5. Publish\n\nAsk the user where tickets go. Two modes:\n\n**Local files** — one file per ticket under `docs\u002Ftickets\u002F\u003Cfeature-slug>\u002F`, numbered from `01`\nin dependency order (blockers first). Use the template in\n[references\u002Fticket-template.md](references\u002Fticket-template.md).\n\n**Issue tracker** (GitHub, Linear, etc.) — publish in dependency order so blocking edges can\nreference real identifiers. Use the platform's native blocking\u002Fsub-issue relationships where\navailable. Confirm with the user before posting — human-in-the-loop applies to anything visible\noutside the local working tree.\n\nWork the frontier: any ticket whose blockers are all done.\n\n## What goes in a ticket\n\n- **What to build**: end-to-end behaviour from the user's perspective, not layer-by-layer\n  implementation steps\n- **Acceptance criteria**: checkboxes, each verifiable\n- **Blocked by**: references to blocking tickets, or \"None (can start immediately)\"\n\nAvoid specific file paths or code snippets — they go stale. Exception: if a prototype produced\na snippet that encodes a decision more precisely than prose (state machine, schema, type shape),\ninline the decision-rich parts and note it came from a prototype.\n\n## Integration\n\n- **[[to-spec]]** produces the spec this skill consumes\n- **[[domain-modeling]]** provides the vocabulary tickets are written in\n- **[[handoff]]** picks up where this leaves off — `handoff add` items from the approved\n  ticket list to seed the backlog for a work session\n",{"name":5,"description":7,"allowed-tools":24,"user-invocable":25,"disable-model-invocation":25},"Read, Grep, Glob, Bash, Write",true,"main","aec70683dacdf9512d27e04a1e04069bbd199b5e","skills\u002Fto-tickets","https:\u002F\u002Fgithub.com\u002Fdannybrown37\u002Fskill-tree","https:\u002F\u002Fgithub.com\u002Fdannybrown37","dannybrown.dev","Software Engineer","2026-11-12 15:25:14",{"source":8,"skillName":5,"commands":35,"prompt":45,"zipAvailable":25},[36,39,42],{"tool":37,"command":38},"npx","npx skills add dannybrown37\u002Fskill-tree --skill to-tickets",{"tool":40,"command":41},"bunx","bunx skills add dannybrown37\u002Fskill-tree --skill to-tickets",{"tool":43,"command":44},"pnpm","pnpm dlx skills add dannybrown37\u002Fskill-tree --skill to-tickets","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fdannybrown37\u002Fskill-tree\u002Fblob\u002Fmain\u002Fskills\u002Fto-tickets\u002FSKILL.md",[47],{"path":48,"resourceType":49,"resourceTypeDesc":50,"sizeBytes":51,"sourceHtmlUrl":52},"references\u002Fticket-template.md","REFERENCE","参考文档",485,"https:\u002F\u002Fgithub.com\u002Fdannybrown37\u002Fskill-tree\u002Fblob\u002Fmain\u002Fskills\u002Fto-tickets\u002Freferences\u002Fticket-template.md",[54,61,68,75,82,89],{"skillNo":55,"name":56,"nameZh":6,"description":57,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":58,"categories":59,"keywords":60,"publishedAt":19},"01M79SQ7Z4DXMYJECV1NTEP9WY","wait-what","Stop. Your plan\u002Fidea did not land. Re-pitch it.","https:\u002F\u002Fgithub.com\u002Fdannybrown37\u002Fskill-tree\u002Fblob\u002Fmain\u002Fskills\u002Fwait-what\u002FSKILL.md",[],[],{"skillNo":62,"name":63,"nameZh":6,"description":64,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":65,"categories":66,"keywords":67,"publishedAt":19},"01M79SQ4WQB5YZ7Q2A87JVR219","verify","Verify before answering whether something works, still passes, is gone, is used, or is correct — and whenever the user says \"can you confirm\", \"are you sure\", \"did that actually work\", or reports something is \"still\" broken. Produces the answer plus the evidence that would have falsified it. A failed GitHub Actions run is skill-tree:debug-ci instead.","https:\u002F\u002Fgithub.com\u002Fdannybrown37\u002Fskill-tree\u002Fblob\u002Fmain\u002Fskills\u002Fverify\u002FSKILL.md",[],[],{"skillNo":69,"name":70,"nameZh":6,"description":71,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":72,"categories":73,"keywords":74,"publishedAt":19},"01M79SQ0GKSM5891DKPXE8J7TZ","ui-designer","Design or restyle a web UI — landing pages, dashboards, docs sites, app chrome — or when the user asks why a site \"looks generic\", \"looks like a template\", or wants it to feel intentional. A running list of design lessons learned, applied as rules rather than suggestions.","https:\u002F\u002Fgithub.com\u002Fdannybrown37\u002Fskill-tree\u002Fblob\u002Fmain\u002Fskills\u002Fui-designer\u002FSKILL.md",[],[],{"skillNo":76,"name":77,"nameZh":6,"description":78,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":79,"categories":80,"keywords":81,"publishedAt":19},"01M79SPVN5C0XYAXWBH9HD1YF1","two-axis-review","Two-axis review of changes since a fixed point (commit, tag, HEAD~N, or default HEAD~1): Standards (does the code follow this repo's conventions?) and Spec (does the code do what it should?). Axes run as parallel sub-agents so neither masks the other. Use when the user says \"review against the spec\", \"does this follow our conventions\", \"standards and spec review\", or \"two-axis review\". Not a correctness bug hunt — that's the built-in `\u002Fcode-review`.","https:\u002F\u002Fgithub.com\u002Fdannybrown37\u002Fskill-tree\u002Fblob\u002Fmain\u002Fskills\u002Ftwo-axis-review\u002FSKILL.md",[],[],{"skillNo":83,"name":84,"nameZh":6,"description":85,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":86,"categories":87,"keywords":88,"publishedAt":19},"01M79SPRT8GV1RPQ2VVR9K08BB","tui-screenshots","Use for generating or refreshing TUI screenshots for docs — \"regenerate the screenshots\", \"the README screenshots are stale\". Drives a Textual\u002FTUI app headlessly and exports SVG. Not for reading a user's screenshot — that is `screenshot`.","https:\u002F\u002Fgithub.com\u002Fdannybrown37\u002Fskill-tree\u002Fblob\u002Fmain\u002Fskills\u002Ftui-screenshots\u002FSKILL.md",[],[],{"skillNo":90,"name":91,"nameZh":6,"description":92,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":93,"categories":94,"keywords":95,"publishedAt":19},"01M79SPH2AAARBSV1VWZJCPMFA","to-spec","A conversation has settled on what to build and it's time to turn it into a written spec — \"turn this into a spec\", \"write this up\", \"spec this out\". Synthesis only: no interview. Pairs well with skill-tree:grill-for-planning, which is where the settled understanding usually comes from.","https:\u002F\u002Fgithub.com\u002Fdannybrown37\u002Fskill-tree\u002Fblob\u002Fmain\u002Fskills\u002Fto-spec\u002FSKILL.md",[],[]]