[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7CVCD62F7FJ8WZQS5PA3E2K":3,"skill-same:01M7CVCD62F7FJ8WZQS5PA3E2K":55},{"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":28,"repositoryHtmlUrl":29,"repositoryHomepageUrl":6,"ownerHtmlUrl":30,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":31,"install":32,"resources":44},"01M7CVCD62F7FJ8WZQS5PA3E2K","plan-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).","TudeOrangBiasa\u002Fskills-for-agents","TudeOrangBiasa","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F125188681?v=4","01M7CV804RMMCVN5M0D4ZCQ6D8","TudeStillLearning!","01M7CV805CRFTQY48WZ6JK57YK",1,"MIT","https:\u002F\u002Fgithub.com\u002FTudeOrangBiasa\u002Fskills-for-agents\u002Fblob\u002Fmain\u002Fskills\u002Fuser-invoked\u002Fplan-tickets\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: plan-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-repo`.\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 the configured verifier 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-repo` 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.\nEvery ticket carries exactly one type (`bug`, `feature`, `enhancement`, `deprecation`), one `## Kompleksitas` section (Big-O in named inputs, gh calls, LLM calls), testable acceptance checkboxes, and `ready-for-agent` plus one risk label. A brief missing any of these is not agent-ready: route it to `needs-info` with one concrete question pointing at the missing section, never to `ready-for-agent`. When the tickets collapse a cleared plan-map, quote the map's Destination and Decisions-so-far verbatim instead of re-asking them; the next `\u002Fwhips` (or ship-runner tick) picks the tickets up into feature or bug flows ending in `opening-a-pr.md` or `ship-pr` with no second fog interview.\n\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 (plus one risk 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>: [\u003Ctipe>] \u003CTicket title>\n\n**Tipe:** bug | feature | enhancement | deprecation\n\n**Kompleksitas:** Big-O in named inputs plus gh and LLM calls, e.g. O(T) tickets, 2 gh calls, 0 LLM calls.\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\n## Tipe\n\nSatu dari `bug`, `feature`, `enhancement`, `deprecation`. Tulis di judul (`[bug]: ...`) atau field Tipe.\n\n## Kompleksitas\n\nSatu bagian biaya: Big-O dalam input bernama, panggilan gh, panggilan LLM (mis. `O(T) tiket, 2 panggilan gh, 0 panggilan LLM`). Tanpa bagian ini tiket belum siap agent.\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-repo`.\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 the configured verifier 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-repo` 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.\nEvery ticket carries exactly one type (`bug`, `feature`, `enhancement`, `deprecation`), one `## Kompleksitas` section (Big-O in named inputs, gh calls, LLM calls), testable acceptance checkboxes, and `ready-for-agent` plus one risk label. A brief missing any of these is not agent-ready: route it to `needs-info` with one concrete question pointing at the missing section, never to `ready-for-agent`. When the tickets collapse a cleared plan-map, quote the map's Destination and Decisions-so-far verbatim instead of re-asking them; the next `\u002Fwhips` (or ship-runner tick) picks the tickets up into feature or bug flows ending in `opening-a-pr.md` or `ship-pr` with no second fog interview.\n\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 (plus one risk 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>: [\u003Ctipe>] \u003CTicket title>\n\n**Tipe:** bug | feature | enhancement | deprecation\n\n**Kompleksitas:** Big-O in named inputs plus gh and LLM calls, e.g. O(T) tickets, 2 gh calls, 0 LLM calls.\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\n## Tipe\n\nSatu dari `bug`, `feature`, `enhancement`, `deprecation`. Tulis di judul (`[bug]: ...`) atau field Tipe.\n\n## Kompleksitas\n\nSatu bagian biaya: Big-O dalam input bernama, panggilan gh, panggilan LLM (mis. `O(T) tiket, 2 panggilan gh, 0 panggilan LLM`). Tanpa bagian ini tiket belum siap agent.\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":24},true,"main","d26d63fb9a1a8091ba1d908b1b35738b60e8be79","skills\u002Fuser-invoked\u002Fplan-tickets",0,"https:\u002F\u002Fgithub.com\u002FTudeOrangBiasa\u002Fskills-for-agents","https:\u002F\u002Fgithub.com\u002FTudeOrangBiasa","2026-11-05 23:44:38",{"source":8,"skillName":5,"commands":33,"prompt":43,"zipAvailable":24},[34,37,40],{"tool":35,"command":36},"npx","npx skills add TudeOrangBiasa\u002Fskills-for-agents --skill plan-tickets",{"tool":38,"command":39},"bunx","bunx skills add TudeOrangBiasa\u002Fskills-for-agents --skill plan-tickets",{"tool":41,"command":42},"pnpm","pnpm dlx skills add TudeOrangBiasa\u002Fskills-for-agents --skill plan-tickets","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FTudeOrangBiasa\u002Fskills-for-agents\u002Fblob\u002Fmain\u002Fskills\u002Fuser-invoked\u002Fplan-tickets\u002FSKILL.md",[45,51],{"path":46,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":49,"sourceHtmlUrl":50},"agents\u002Fopenai.yaml","REFERENCE","参考文档",146,"https:\u002F\u002Fgithub.com\u002FTudeOrangBiasa\u002Fskills-for-agents\u002Fblob\u002Fmain\u002Fskills\u002Fuser-invoked\u002Fplan-tickets\u002Fagents\u002Fopenai.yaml",{"path":52,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":53,"sourceHtmlUrl":54},"CREDITS.md",467,"https:\u002F\u002Fgithub.com\u002FTudeOrangBiasa\u002Fskills-for-agents\u002Fblob\u002Fmain\u002Fskills\u002Fuser-invoked\u002Fplan-tickets\u002FCREDITS.md",[56,63,70,77,84,91],{"skillNo":57,"name":58,"nameZh":6,"description":59,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":60,"categories":61,"keywords":62,"publishedAt":19},"01M7CVDKFYKNEY024TK36QAA2R","whips","Route any non-trivial task through one entry: match a playbook, drive HIT skills plus subagents, open a reviewed ready PR with ship-pr-shaped evidence.","https:\u002F\u002Fgithub.com\u002FTudeOrangBiasa\u002Fskills-for-agents\u002Fblob\u002Fmain\u002Fskills\u002Fuser-invoked\u002Fwhips\u002FSKILL.md",[],[],{"skillNo":64,"name":65,"nameZh":6,"description":66,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":67,"categories":68,"keywords":69,"publishedAt":19},"01M7CVDFG46BBHV71Q5JVZ7XZT","verify-upkeep","Periodic upkeep for a project's verification skill: source wave plus live pass per feature, at most one PR of proven corrections. Use to audit the verify skill.","https:\u002F\u002Fgithub.com\u002FTudeOrangBiasa\u002Fskills-for-agents\u002Fblob\u002Fmain\u002Fskills\u002Fuser-invoked\u002Fverify-upkeep\u002FSKILL.md",[],[],{"skillNo":71,"name":72,"nameZh":6,"description":73,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":74,"categories":75,"keywords":76,"publishedAt":19},"01M7CVDB20QNGAPR8T5YXDRNT9","verify-statechart","Check a TLA+ model of a system that moves between states, such as a product flow, a protocol, or a service, and draw it as a Mermaid statechart. The report gives the shortest path to each state that breaks a rule. Use to show a bug as a path through states.","https:\u002F\u002Fgithub.com\u002FTudeOrangBiasa\u002Fskills-for-agents\u002Fblob\u002Fmain\u002Fskills\u002Fuser-invoked\u002Fverify-statechart\u002FSKILL.md",[],[],{"skillNo":78,"name":79,"nameZh":6,"description":80,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":81,"categories":82,"keywords":83,"publishedAt":19},"01M7CVD6Y3W2A12ZDEQBS39QPD","verify-new","Generate a project-local skill that drives the app like a user (launch, doctor, drive, evidence, feature map), proven once. Use when a project has no scripted proof.","https:\u002F\u002Fgithub.com\u002FTudeOrangBiasa\u002Fskills-for-agents\u002Fblob\u002Fmain\u002Fskills\u002Fuser-invoked\u002Fverify-new\u002FSKILL.md",[],[],{"skillNo":85,"name":86,"nameZh":6,"description":87,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":88,"categories":89,"keywords":90,"publishedAt":19},"01M7CVD2WTQ83ETMQ82GWWZAAV","ship-triage","Move issues and external PRs through a state machine of triage roles, categorise, verify, interview if needed, and write agent-ready briefs.","https:\u002F\u002Fgithub.com\u002FTudeOrangBiasa\u002Fskills-for-agents\u002Fblob\u002Fmain\u002Fskills\u002Fuser-invoked\u002Fship-triage\u002FSKILL.md",[],[],{"skillNo":92,"name":93,"nameZh":6,"description":94,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":95,"categories":96,"keywords":97,"publishedAt":19},"01M7CVCYS0S8S8XW68V819QKZ6","ship-runner","Run ready-for-agent issue queues on any schedule through \u002Fwhips intake, one fresh worktree each, landing per risk tier, with the agent and model you pick at setup.","https:\u002F\u002Fgithub.com\u002FTudeOrangBiasa\u002Fskills-for-agents\u002Fblob\u002Fmain\u002Fskills\u002Fuser-invoked\u002Fship-runner\u002FSKILL.md",[],[]]