[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6PDRK5GJHTT33KDH4G6ZHTR":3,"skill-same:01M6PDRK5GJHTT33KDH4G6ZHTR":67},{"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":38,"linkOnly":39,"markdownContent":40,"markdownBody":41,"frontMatter":42,"refName":43,"commitSha":44,"skillDirectory":45,"forksCount":46,"repositoryHtmlUrl":47,"repositoryHomepageUrl":48,"ownerHtmlUrl":49,"ownerBlogUrl":50,"ownerDescription":51,"updatedAt":52,"install":53,"resources":66},"01M6PDRK5GJHTT33KDH4G6ZHTR","to-issues",null,"Break a plan, spec, or PRD into independently-grabbable issues on the project issue tracker using tracer-bullet vertical slices. Use when user wants to convert a plan into issues, create implementation tickets, or break down work into issues.","stevesolun\u002Fctx","stevesolun","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F1304538?v=4","01M6PDDJQ35XAXMPJQP8YG3P2X","Steve Solun","01M6PDDJVJ663A3CMV7XQN9XAY",590,"MIT","https:\u002F\u002Fgithub.com\u002Fstevesolun\u002Fctx\u002Fblob\u002Fmain\u002Fimported-skills\u002Fmattpocock\u002Fto-issues\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37],"to issues","issues","down","spec","break","issue tracker","break down","tickets","project","tracker","issue","implementation","use","user","work","convert","plan","prd","create","2026-11-10 10:12:30",false,"---\nname: to-issues\ndescription: Break a plan, spec, or PRD into independently-grabbable issues on the project issue tracker using tracer-bullet vertical slices. Use when user wants to convert a plan into issues, create implementation tickets, or break down work into issues.\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 `\u002Fsetup-matt-pocock-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 an issue reference (issue number, URL, or path) as an argument, fetch it from the issue tracker 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. 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. Quiz the user\n\nPresent the proposed breakdown as a numbered list. For each slice, show:\n\n- **Title**: short descriptive name\n- **Type**: HITL \u002F AFK\n- **Blocked by**: which other slices (if any) must complete first\n- **User stories covered**: which user stories this addresses (if the source material has them)\n\nAsk the user:\n\n- Does the granularity feel right? (too coarse \u002F too fine)\n- Are the dependency relationships correct?\n- Should any slices be merged or split further?\n- Are the correct slices marked as HITL and AFK?\n\nIterate until the user approves the breakdown.\n\n### 5. Publish the issues to the issue tracker\n\nFor each approved slice, publish a new issue to the issue tracker. Use the issue body template below. These issues are considered ready for AFK agents, so publish them with the correct triage label unless instructed otherwise.\n\nPublish issues in dependency order (blockers first) so you can reference real issue identifiers in the \"Blocked by\" field.\n\n\u003Cissue-template>\n## Parent\n\nA reference to the parent issue 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## 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","# 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 `\u002Fsetup-matt-pocock-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 an issue reference (issue number, URL, or path) as an argument, fetch it from the issue tracker 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. 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. Quiz the user\n\nPresent the proposed breakdown as a numbered list. For each slice, show:\n\n- **Title**: short descriptive name\n- **Type**: HITL \u002F AFK\n- **Blocked by**: which other slices (if any) must complete first\n- **User stories covered**: which user stories this addresses (if the source material has them)\n\nAsk the user:\n\n- Does the granularity feel right? (too coarse \u002F too fine)\n- Are the dependency relationships correct?\n- Should any slices be merged or split further?\n- Are the correct slices marked as HITL and AFK?\n\nIterate until the user approves the breakdown.\n\n### 5. Publish the issues to the issue tracker\n\nFor each approved slice, publish a new issue to the issue tracker. Use the issue body template below. These issues are considered ready for AFK agents, so publish them with the correct triage label unless instructed otherwise.\n\nPublish issues in dependency order (blockers first) so you can reference real issue identifiers in the \"Blocked by\" field.\n\n\u003Cissue-template>\n## Parent\n\nA reference to the parent issue 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## 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",{"name":5,"description":7},"main","11b582a7cd4d549f1e83c412e04421bcc9c3fc28","imported-skills\u002Fmattpocock\u002Fto-issues",69,"https:\u002F\u002Fgithub.com\u002Fstevesolun\u002Fctx","https:\u002F\u002Fstevesolun.github.io\u002Fctx\u002F","https:\u002F\u002Fgithub.com\u002Fstevesolun","https:\u002F\u002Fwww.linkedin.com\u002Fin\u002Fsolunsteve\u002F","High motivated, dedicated, fast learner data scientist and enthusiastic researcher.","2026-10-15 03:55:28",{"source":8,"skillName":5,"commands":54,"prompt":64,"zipAvailable":65},[55,58,61],{"tool":56,"command":57},"npx","npx skills add stevesolun\u002Fctx --skill to-issues",{"tool":59,"command":60},"bunx","bunx skills add stevesolun\u002Fctx --skill to-issues",{"tool":62,"command":63},"pnpm","pnpm dlx skills add stevesolun\u002Fctx --skill to-issues","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fstevesolun\u002Fctx\u002Fblob\u002Fmain\u002Fimported-skills\u002Fmattpocock\u002Fto-issues\u002FSKILL.md",true,[],[68,93,116,142,167,188],{"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":38},"01M6PDTT7F6Z9T6G6H92845RNC","toolbox","Pre\u002Fpost dev toolbox — named bundles of skills\u002Fagents loaded before development work and councils of experts invoked after. Run \u002Ftoolbox or the toolbox.py CLI to list, activate, initialize, export, import, and validate toolboxes. Invoke at the start or end of a dev session, when setting up a new repo, or when sharing toolboxes with a team.","https:\u002F\u002Fgithub.com\u002Fstevesolun\u002Fctx\u002Fblob\u002Fmain\u002Fskills\u002Ftoolbox\u002FSKILL.md",[],[70,75,76,77,78,79,33,80,81,82,83,84,85,86,87,88,89,90,91,92],"cli","development","run","start","team","list","initialize","export","up","activate","feature","end","new repo","false","import","experts","at","invoke",{"skillNo":94,"name":95,"nameZh":6,"description":96,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":97,"categories":98,"keywords":104,"publishedAt":38},"01M6PDTNZ10BAW6VY49S40NCBB","skill-router","Alive skill router — reads the current project's stack and loads\u002Funloads skills dynamically. Invoke at session start or when project context changes.","https:\u002F\u002Fgithub.com\u002Fstevesolun\u002Fctx\u002Fblob\u002Fmain\u002Fskills\u002Fskill-router\u002FSKILL.md",[99],{"categoryNo":100,"categoryName":101,"taxonomyType":102,"taxonomyTypeDesc":103},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[105,106,78,107,108,109,110,111,27,112,113,114,91,115,92],"router","skill router","Meta","stack","context","session","project context","loads","session start","true","changes",{"skillNo":117,"name":118,"nameZh":6,"description":119,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":120,"categories":121,"keywords":123,"publishedAt":38},"01M6PDTGVDG503T4QNX64KJMAC","repo-stats-autoupdate","Keeps README badge + inline counts in sync with the real number of skills, agents, graph nodes\u002Fedges, communities, converted pipelines, and test inventory. Runs automatically on every commit via a git pre-commit hook. Use when the README drifts from reality or before publishing a release.","https:\u002F\u002Fgithub.com\u002Fstevesolun\u002Fctx\u002Fblob\u002Fmain\u002Fskills\u002Frepo-stats-autoupdate\u002FSKILL.md",[122],{"categoryNo":100,"categoryName":101,"taxonomyType":102,"taxonomyTypeDesc":103},[124,125,126,127,128,129,130,131,132,133,134,135,31,136,137,88,138,139,140,141],"stats","repo","repo stats autoupdate","test","commit","sync","release","git","graph","pre-commit","inventory","README","publishing","communities","with","hook","number","inline",{"skillNo":143,"name":144,"nameZh":6,"description":145,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":146,"categories":147,"keywords":154,"publishedAt":38},"01M6PDTC3AB7H4NXJFS3SDKQG9","find-skills","Discover installable agent skills from ctx's shipped Skills.sh catalog, the Skills.sh search API, and the npx skills CLI. Use when a user asks whether a skill exists, wants to add\u002Fupdate a skill, or needs a repeatable procedure for finding candidate skills safely.","https:\u002F\u002Fgithub.com\u002Fstevesolun\u002Fctx\u002Fblob\u002Fmain\u002Fskills\u002Ffind-skills\u002FSKILL.md",[148,149],{"categoryNo":100,"categoryName":101,"taxonomyType":102,"taxonomyTypeDesc":103},{"categoryNo":150,"categoryName":151,"taxonomyType":152,"taxonomyTypeDesc":153},"01JBSEEDCAT000000000000030","开发工程师","PROFESSION","适用职业",[155,156,75,157,158,159,32,160,31,56,161,162,163,164,165,166],"find skills","find","update","search","api","catalog","discover","add","skills cli","for","candidate","ctx",{"skillNo":168,"name":169,"nameZh":6,"description":170,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":171,"categories":172,"keywords":173,"publishedAt":38},"01M6PDT6ETDH54GGY7K8E29Y9V","no-mistakes","Validate committed feature-branch changes through the no-mistakes pipeline: intent, rebase, review, test, docs, lint, push, PR, and CI. Use when the user asks to run no-mistakes, ship safely, validate before pushing, or gate a change before it reaches upstream.","https:\u002F\u002Fgithub.com\u002Fstevesolun\u002Fctx\u002Fblob\u002Fmain\u002Fimported-skills\u002Fno-mistakes\u002Fskills\u002Fno-mistakes\u002FSKILL.md",[],[174,175,127,176,177,178,77,179,180,181,182,183,184,185,31,186,187,85,114,115],"no mistakes","review","change","validate","pr","lint","push","ci","pipeline","ship","rebase","branch","intent","upstream",{"skillNo":189,"name":190,"nameZh":6,"description":191,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":192,"categories":193,"keywords":196,"publishedAt":38},"01M6PDT18DD3HETZF1CF39CT8J","zoom-out","Tell the agent to zoom out and give broader context or a higher-level perspective. Use when you're unfamiliar with a section of code or need to understand how it fits into the bigger picture.","https:\u002F\u002Fgithub.com\u002Fstevesolun\u002Fctx\u002Fblob\u002Fmain\u002Fimported-skills\u002Fmattpocock\u002Fzoom-out\u002FSKILL.md",[194,195],{"categoryNo":100,"categoryName":101,"taxonomyType":102,"taxonomyTypeDesc":103},{"categoryNo":150,"categoryName":151,"taxonomyType":152,"taxonomyTypeDesc":153},[197,198,199,200,109,31,201,202,138,203,204,114,205,206],"zoom out","zoom","code","how","it","understand","you","re","perspective","section"]