[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6R5WVJ13K6C69SERMHG736K":3,"skill-same:01M6R5WVJ13K6C69SERMHG736K":56},{"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":31,"linkOnly":32,"markdownContent":33,"markdownBody":34,"frontMatter":35,"refName":36,"commitSha":37,"skillDirectory":38,"forksCount":13,"repositoryHtmlUrl":39,"repositoryHomepageUrl":6,"ownerHtmlUrl":40,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":41,"install":42,"resources":55},"01M6R5WVJ13K6C69SERMHG736K","to-issues",null,"Break a plan, spec, or PRD into traceable implementation issues. Use when converting requirements into tickets or agent-ready work.","r3dlex\u002Fskills","r3dlex","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F291373160?v=4","01M6PEFNGGBVB7SHAPWXFFX933","01M6R5SDWFHT94734KJFMYE1SX",0,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fr3dlex\u002Fskills\u002Fblob\u002Fmain\u002F02-govern-plan\u002Fto-issues\u002FSKILL.md",[],[18,19,20,21,22,23,24,25,26,27,28,29,30],"to issues","issues","spec","prd","plan","work","use","ready","implementation","requirements","tickets","break","when","2026-11-10 10:12:30",false,"---\nname: to-issues\ndescription: 'Break a plan, spec, or PRD into traceable implementation issues. Use when converting requirements into tickets or agent-ready work.'\n---\n\n# To Issues\n\nBreak a plan into independently-grabbable issues using vertical slices (tracer bullets).\n\nThe issue tracker and triage label vocabulary should have been provided to you — run `setup-skills` if not.\n\n## Process\n\n### 1. Gather context\n\nWork from whatever is already in the conversation context. If the user passes a BRD, PRD, issue reference, work item ID, URL, or path as an argument, fetch it from the issue tracker and read its full body, comments, and traceability links.\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. Issue titles and descriptions should use the project's domain glossary vocabulary, and respect ADRs in the area you're touching.\n\n### 3. Draft vertical slices\n\nBreak the plan into **tracer bullet** issues. Each issue is a thin vertical slice that cuts through ALL integration layers end-to-end, NOT a horizontal slice of one layer.\n\nSlices may be 'HITL' or 'AFK'. HITL slices require human interaction, such as an architectural decision or a design review. AFK slices can be implemented and merged without human interaction. Prefer AFK over HITL where possible.\n\n\u003Cvertical-slice-rules>\n- Each slice delivers a narrow but COMPLETE path through every layer (schema, API, UI, tests)\n- A completed slice is demoable or verifiable on its own\n- Prefer many thin slices over few thick ones\n\u003C\u002Fvertical-slice-rules>\n\n### 4. Publish\n\nPublish issues\u002Fwork items directly to the issue tracker in dependency order (blockers first), preserving BRD and PRD backlinks in each body. If the user asked for review first, show the list before publishing. Otherwise, publish with sensible defaults:\n\n- **Granularity**: prefer many thin slices over few thick ones\n- **Type**: default to AFK; mark HITL only when a human decision is genuinely required\n- **Blockers**: express dependencies as a DAG, not a chain\n\nFor each slice, use the issue body template below. Apply the `ready-for-agent` triage label unless instructed otherwise.\n\n\u003Cissue-template>\n## Traceability\n\n- BRD: \u003CBRD ID\u002Flink, or \"None provided\">\n- PRD: \u003CPRD ID\u002Flink>\n- Parent: \u003Cparent issue\u002Fwork item, or \"None\">\n- Version impact: \u003Ccopy from PRD\u002Fspec, or \"unknown\">\n\n## Parent\n\nA reference to the parent issue\u002Fwork item on the issue tracker (if the source was an existing issue, otherwise omit this section).\n\n## What to build\n\nA concise description of this vertical slice. Describe the end-to-end behavior, not layer-by-layer implementation.\n\nAvoid 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 here 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## Acceptance criteria\n\n- [ ] Criterion 1\n- [ ] Criterion 2\n- [ ] Criterion 3\n\n## Version impact\n\nCopy the highest available PRD\u002Fspec\u002FADR\u002Facceptance-criteria signal. If the slice appears lower-impact than the parent PRD\u002Fspec, keep the higher signal and note the conflict; do not downgrade from commit\u002Fdiff inference alone.\n\n## Blocked by\n\n- A reference to the blocking ticket (if any)\n\nOr \"None - can start immediately\" if no blockers.\n\n\u003C\u002Fissue-template>\n\nDo NOT close or modify any parent issue.\n\nEnd by declaring knowledge kind `plan`, then reading\n[ai-catapult-init\u002Fmodules\u002Fknowledge-publish.md](..\u002Fai-catapult-init\u002Fmodules\u002Fknowledge-publish.md) and running its host-neutral producer step — publish when a registry exists, otherwise record `unpublished: \u003Creason>`; never fail the skill because of the registry.\n","# To Issues\n\nBreak a plan into independently-grabbable issues using vertical slices (tracer bullets).\n\nThe issue tracker and triage label vocabulary should have been provided to you — run `setup-skills` if not.\n\n## Process\n\n### 1. Gather context\n\nWork from whatever is already in the conversation context. If the user passes a BRD, PRD, issue reference, work item ID, URL, or path as an argument, fetch it from the issue tracker and read its full body, comments, and traceability links.\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. Issue titles and descriptions should use the project's domain glossary vocabulary, and respect ADRs in the area you're touching.\n\n### 3. Draft vertical slices\n\nBreak the plan into **tracer bullet** issues. Each issue is a thin vertical slice that cuts through ALL integration layers end-to-end, NOT a horizontal slice of one layer.\n\nSlices may be 'HITL' or 'AFK'. HITL slices require human interaction, such as an architectural decision or a design review. AFK slices can be implemented and merged without human interaction. Prefer AFK over HITL where possible.\n\n\u003Cvertical-slice-rules>\n- Each slice delivers a narrow but COMPLETE path through every layer (schema, API, UI, tests)\n- A completed slice is demoable or verifiable on its own\n- Prefer many thin slices over few thick ones\n\u003C\u002Fvertical-slice-rules>\n\n### 4. Publish\n\nPublish issues\u002Fwork items directly to the issue tracker in dependency order (blockers first), preserving BRD and PRD backlinks in each body. If the user asked for review first, show the list before publishing. Otherwise, publish with sensible defaults:\n\n- **Granularity**: prefer many thin slices over few thick ones\n- **Type**: default to AFK; mark HITL only when a human decision is genuinely required\n- **Blockers**: express dependencies as a DAG, not a chain\n\nFor each slice, use the issue body template below. Apply the `ready-for-agent` triage label unless instructed otherwise.\n\n\u003Cissue-template>\n## Traceability\n\n- BRD: \u003CBRD ID\u002Flink, or \"None provided\">\n- PRD: \u003CPRD ID\u002Flink>\n- Parent: \u003Cparent issue\u002Fwork item, or \"None\">\n- Version impact: \u003Ccopy from PRD\u002Fspec, or \"unknown\">\n\n## Parent\n\nA reference to the parent issue\u002Fwork item on the issue tracker (if the source was an existing issue, otherwise omit this section).\n\n## What to build\n\nA concise description of this vertical slice. Describe the end-to-end behavior, not layer-by-layer implementation.\n\nAvoid 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 here 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## Acceptance criteria\n\n- [ ] Criterion 1\n- [ ] Criterion 2\n- [ ] Criterion 3\n\n## Version impact\n\nCopy the highest available PRD\u002Fspec\u002FADR\u002Facceptance-criteria signal. If the slice appears lower-impact than the parent PRD\u002Fspec, keep the higher signal and note the conflict; do not downgrade from commit\u002Fdiff inference alone.\n\n## Blocked by\n\n- A reference to the blocking ticket (if any)\n\nOr \"None - can start immediately\" if no blockers.\n\n\u003C\u002Fissue-template>\n\nDo NOT close or modify any parent issue.\n\nEnd by declaring knowledge kind `plan`, then reading\n[ai-catapult-init\u002Fmodules\u002Fknowledge-publish.md](..\u002Fai-catapult-init\u002Fmodules\u002Fknowledge-publish.md) and running its host-neutral producer step — publish when a registry exists, otherwise record `unpublished: \u003Creason>`; never fail the skill because of the registry.\n",{"name":5,"description":7},"main","037fe34299eb9c4a30b51f1a6bd101eae1c469b1","02-govern-plan\u002Fto-issues","https:\u002F\u002Fgithub.com\u002Fr3dlex\u002Fskills","https:\u002F\u002Fgithub.com\u002Fr3dlex","2026-10-29 16:22:54",{"source":8,"skillName":5,"commands":43,"prompt":53,"zipAvailable":54},[44,47,50],{"tool":45,"command":46},"npx","npx skills add r3dlex\u002Fskills --skill to-issues",{"tool":48,"command":49},"bunx","bunx skills add r3dlex\u002Fskills --skill to-issues",{"tool":51,"command":52},"pnpm","pnpm dlx skills add r3dlex\u002Fskills --skill to-issues","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fr3dlex\u002Fskills\u002Fblob\u002Fmain\u002F02-govern-plan\u002Fto-issues\u002FSKILL.md",true,[],[57,65,78,87,97,120],{"skillNo":58,"name":59,"nameZh":6,"description":60,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":61,"categories":62,"keywords":63,"publishedAt":31},"01M6R652E42RZT7M2V3RWW991Z","skill","Fixture.","https:\u002F\u002Fgithub.com\u002Fr3dlex\u002Fskills\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Fcatalog-malformed\u002Fskill\u002FSKILL.md",[],[64],"fixture",{"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":76,"publishedAt":31},"01M6R64MTPF0FGWHFS4DWP40GR","stable-skill","Fixture stable-skill.","https:\u002F\u002Fgithub.com\u002Fr3dlex\u002Fskills\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Fcatalog-lifecycle\u002Fstable-skill\u002FSKILL.md",[71],{"categoryNo":72,"categoryName":73,"taxonomyType":74,"taxonomyTypeDesc":75},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[77,64],"stable skill",{"skillNo":79,"name":80,"nameZh":6,"description":81,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":82,"categories":83,"keywords":85,"publishedAt":31},"01M6R64HD4QVAYM2R0JSYNVDJW","experimental-skill","Fixture experimental-skill.","https:\u002F\u002Fgithub.com\u002Fr3dlex\u002Fskills\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Fcatalog-lifecycle\u002Fexperimental-skill\u002FSKILL.md",[84],{"categoryNo":72,"categoryName":73,"taxonomyType":74,"taxonomyTypeDesc":75},[86,64],"experimental skill",{"skillNo":88,"name":89,"nameZh":6,"description":90,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":91,"categories":92,"keywords":94,"publishedAt":31},"01M6R64FZH05TEJQW75QX1E5XD","deprecated-skill","Fixture deprecated-skill.","https:\u002F\u002Fgithub.com\u002Fr3dlex\u002Fskills\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Fcatalog-lifecycle\u002Fdeprecated-skill\u002FSKILL.md",[93],{"categoryNo":72,"categoryName":73,"taxonomyType":74,"taxonomyTypeDesc":75},[95,96,64],"deprecated skill","deprecated",{"skillNo":98,"name":99,"nameZh":6,"description":100,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":101,"categories":102,"keywords":103,"publishedAt":31},"01M6R64D13X5DC980GREWFSSFQ","karpathy-guidelines","Apply think-before-coding, simplicity, surgical-change, and goal-driven engineering rules. Use when planning, implementing, or reviewing code.","https:\u002F\u002Fgithub.com\u002Fr3dlex\u002Fskills\u002Fblob\u002Fmain\u002Freference\u002Fgolden-skills\u002F.agents\u002Fskills\u002Fkarpathy-guidelines\u002FSKILL.md",[],[104,105,106,107,24,108,109,110,111,112,113,114,30,115,116,117,118,119],"karpathy guidelines","karpathy","guidelines","Rules","simplicity","goal","think","driven","reviewing code","implementing","apply","coding","change","code","planning","engineering",{"skillNo":121,"name":99,"nameZh":6,"description":100,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":122,"categories":123,"keywords":124,"publishedAt":31},"01M6R640ZS60BRV9P49FT46ZJX","https:\u002F\u002Fgithub.com\u002Fr3dlex\u002Fskills\u002Fblob\u002Fmain\u002Freference\u002Fgolden-root\u002F.agents\u002Fskills\u002Fkarpathy-guidelines\u002FSKILL.md",[],[106,104,105,116,111,117,118,119,115,107,24,108,109,110,112,113,114,30]]