[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M72W60EP8VC16C50PXYXJC5D":3,"skill-same:01M72W60EP8VC16C50PXYXJC5D":44},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":18,"linkOnly":19,"markdownContent":20,"markdownBody":21,"frontMatter":22,"refName":23,"commitSha":24,"skillDirectory":25,"forksCount":26,"repositoryHtmlUrl":27,"repositoryHomepageUrl":6,"ownerHtmlUrl":28,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":29,"install":30,"resources":43},"01M72W60EP8VC16C50PXYXJC5D","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.","libz-renlab-ai\u002FMatrix-Viki","libz-renlab-ai","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F277592717?v=4","01M71ENHYC54KKYC8Q3KDYG8S2","01M72W199DPMZF71MDAXQMVEY2",1,"MIT","https:\u002F\u002Fgithub.com\u002Flibz-renlab-ai\u002FMatrix-Viki\u002Fblob\u002Fmain\u002F.codex\u002Fskills\u002Fto-issues\u002FSKILL.md",[],[],"2026-11-10 22:39:42",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","2ff5f3d80eff5adb8e7166cfb1182707e8098af2",".codex\u002Fskills\u002Fto-issues",0,"https:\u002F\u002Fgithub.com\u002Flibz-renlab-ai\u002FMatrix-Viki","https:\u002F\u002Fgithub.com\u002Flibz-renlab-ai","2026-05-20 13:23:26",{"source":8,"skillName":5,"commands":31,"prompt":41,"zipAvailable":42},[32,35,38],{"tool":33,"command":34},"npx","npx skills add libz-renlab-ai\u002FMatrix-Viki --skill to-issues",{"tool":36,"command":37},"bunx","bunx skills add libz-renlab-ai\u002FMatrix-Viki --skill to-issues",{"tool":39,"command":40},"pnpm","pnpm dlx skills add libz-renlab-ai\u002FMatrix-Viki --skill to-issues","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Flibz-renlab-ai\u002FMatrix-Viki\u002Fblob\u002Fmain\u002F.codex\u002Fskills\u002Fto-issues\u002FSKILL.md",true,[],[45,52,59,66,73,80],{"skillNo":46,"name":47,"nameZh":6,"description":48,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":49,"categories":50,"keywords":51,"publishedAt":18},"01M72W66NEM357BYZZ2KQWKMK5","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\u002Flibz-renlab-ai\u002FMatrix-Viki\u002Fblob\u002Fmain\u002F.codex\u002Fskills\u002Fzoom-out\u002FSKILL.md",[],[],{"skillNo":53,"name":54,"nameZh":6,"description":55,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":56,"categories":57,"keywords":58,"publishedAt":18},"01M72W64QAPK9T1R0PQAA5FVGP","triage","Triage issues through a state machine driven by triage roles. Use when user wants to create an issue, triage issues, review incoming bugs or feature requests, prepare issues for an AFK agent, or manage issue workflow.","https:\u002F\u002Fgithub.com\u002Flibz-renlab-ai\u002FMatrix-Viki\u002Fblob\u002Fmain\u002F.codex\u002Fskills\u002Ftriage\u002FSKILL.md",[],[],{"skillNo":60,"name":61,"nameZh":6,"description":62,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":63,"categories":64,"keywords":65,"publishedAt":18},"01M72W62GXS5BKZ9HDKWGT8R9C","to-prd","Turn the current conversation context into a PRD and publish it to the project issue tracker. Use when user wants to create a PRD from the current context.","https:\u002F\u002Fgithub.com\u002Flibz-renlab-ai\u002FMatrix-Viki\u002Fblob\u002Fmain\u002F.codex\u002Fskills\u002Fto-prd\u002FSKILL.md",[],[],{"skillNo":67,"name":68,"nameZh":6,"description":69,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":70,"categories":71,"keywords":72,"publishedAt":18},"01M72W5V80MPEMH126EPFRMYM5","reverification","By-hand only — DO NOT auto-trigger. When the user types \u002Freverification (or asks\nfor \"reverify this\", \"independent verification\", \"LLM-uncheatable check\",\n\"第三方再验证\", \"用 repo 之外的方法验证\"), re-verify recently-completed work\nusing verification methods that **existed before this repo existed** and that an\nLLM agent cannot fabricate. Pick 3-5 verifications from a 10-family menu\n(hardware \u002F cryptographic \u002F blockchain \u002F external real-system \u002F mathematical \u002F\ntemporal \u002F content authenticity \u002F physical \u002F network \u002F third-party trust),\ndispatch them via real tools that capture raw evidence, and report PASS \u002F FAIL \u002F\nINCONCLUSIVE based ONLY on captured evidence — never on internal reasoning.\nRefuse to fall back on TeamBrain's bespoke verifiers (judge harness, fastprobe,\n\u002Freview, feature-verification gates) because those did NOT exist before the repo.","https:\u002F\u002Fgithub.com\u002Flibz-renlab-ai\u002FMatrix-Viki\u002Fblob\u002Fmain\u002F.codex\u002Fskills\u002Freverification\u002FSKILL.md",[],[],{"skillNo":74,"name":75,"nameZh":6,"description":76,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":77,"categories":78,"keywords":79,"publishedAt":18},"01M72W5RB0B7C5YWPMYQFQBTFP","repo-issues-status","TeamBrain 仓库**全量 issue 全景**报告（all-scope only）。仅当用户问\"status of all issues\" \u002F \"show me all issues\" \u002F \"what issues are open\" \u002F \"all open issues\" \u002F \"issue 状态（全景）\" \u002F \"所有 issue 状态\" \u002F \"issue 全景\" \u002F \"仓库 issue 概览\" \u002F \"还有哪些 open issue\" 这类**仓库级、多 issue、概览类**问题时触发。**不要在以下情况触发**：(a) 用户问单个 issue 的状态（\"what's the status of issue","https:\u002F\u002Fgithub.com\u002Flibz-renlab-ai\u002FMatrix-Viki\u002Fblob\u002Fmain\u002F.codex\u002Fskills\u002Frepo-issues-status\u002FSKILL.md",[],[],{"skillNo":81,"name":82,"nameZh":6,"description":83,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":84,"categories":85,"keywords":86,"publishedAt":18},"01M72W5NH517EEMA4PZYHMN5NN","prototype","Build a throwaway prototype to flush out a design before committing to it. Routes between two branches — a runnable terminal app for state\u002Fbusiness-logic questions, or several radically different UI variations toggleable from one route. Use when the user wants to prototype, sanity-check a data model or state machine, mock up a UI, explore design options, or says \"prototype this\", \"let me play with it\", \"try a few designs\".","https:\u002F\u002Fgithub.com\u002Flibz-renlab-ai\u002FMatrix-Viki\u002Fblob\u002Fmain\u002F.codex\u002Fskills\u002Fprototype\u002FSKILL.md",[],[]]