[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M71NSKPB8BRYRJ8DSXT6GSCS":3,"skill-same:01M71NSKPB8BRYRJ8DSXT6GSCS":57},{"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":30,"linkOnly":31,"markdownContent":32,"markdownBody":33,"frontMatter":34,"refName":37,"commitSha":38,"skillDirectory":39,"forksCount":13,"repositoryHtmlUrl":40,"repositoryHomepageUrl":6,"ownerHtmlUrl":41,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":42,"install":43,"resources":56},"01M71NSKPB8BRYRJ8DSXT6GSCS","to-issues",null,"Use when the user wants to break a plan, spec, or PRD into independently-grabbable GitHub issues using tracer-bullet vertical slices.","max-kharena\u002Fnous","max-kharena","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F249811097?v=4","01M71NQQ2DRKPEV4AF9J318N31","01M71NQQ303XV5QX5DHCZKM41V",0,"MIT","https:\u002F\u002Fgithub.com\u002Fmax-kharena\u002Fnous\u002Fblob\u002Fmain\u002Fskills\u002Fto-issues\u002FSKILL.md",[],[18,19,20,21,22,23,24,25,26,27,28,29],"to issues","issues","plan","github","planning","break","spec","use","when","prd","github issues","user","2026-11-10 10:56:23",false,"---\nname: to-issues\ndescription: Use when the user wants to break a plan, spec, or PRD into independently-grabbable GitHub issues using tracer-bullet vertical slices.\nversion: 0.1.0\ntype: planning\nrisk: medium\n---\n\n# To Issues\n\nBreak a plan into independently-grabbable GitHub issues using **vertical slices** (tracer bullets). Each issue cuts end-to-end through every layer, not horizontally through one layer.\n\n## Workflow\n\n### 1. Gather context\n\nWork from whatever is already in the conversation. If the user passes a GitHub issue number or URL, fetch it with `gh issue view \u003Cnumber>` (with comments). If a NOUS plan file exists at `.nous\u002Fplans\u002F\u003Cdomain>-plan.md` or `docs\u002Fnous\u002Fplans\u002F\u003Cdomain>-plan.md`, read it.\n\n### 2. Explore the codebase (optional)\n\nIf you have not already explored the codebase, do so to understand current state.\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 (schema, API, UI, tests), NOT a horizontal slice of one layer.\n\nSlices may be **HITL** or **AFK**:\n\n- **HITL** — Human In The Loop. Requires architectural decision, design review, or judgment call.\n- **AFK** — Away From Keyboard. Can be implemented and merged without human interaction.\n\nPrefer 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 has them)\n\nAsk:\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 HITL vs AFK?\n\nIterate until the user approves the breakdown.\n\n### 5. Create the GitHub issues\n\nFor each approved slice, create a GitHub issue with `gh issue create`. Use the body template below.\n\nCreate issues **in dependency order** (blockers first) so you can reference real issue numbers in the \"Blocked by\" field.\n\n## Issue template\n\n```md\n## Parent\n\n#\u003Cparent-issue-number> (omit this section if there is no parent)\n\n## What to build\n\nConcise description of this vertical slice. Describe end-to-end behavior, not layer-by-layer implementation.\n\n## Acceptance criteria\n\n- [ ] Criterion 1\n- [ ] Criterion 2\n- [ ] Criterion 3\n\n## Blocked by\n\n- Blocked by #\u003Cissue-number> (if any)\n\nOr \"None — can start immediately\" if no blockers.\n```\n\n## Rules\n\n- Do NOT close or modify the parent issue.\n- No file paths or line numbers in the issue body — describe behaviors and contracts.\n- Use the project's domain language (`UBIQUITOUS_LANGUAGE.md` \u002F `CONTEXT.md` if present).\n- After filing, print all issue URLs with blocking relationships summarized.\n","# To Issues\n\nBreak a plan into independently-grabbable GitHub issues using **vertical slices** (tracer bullets). Each issue cuts end-to-end through every layer, not horizontally through one layer.\n\n## Workflow\n\n### 1. Gather context\n\nWork from whatever is already in the conversation. If the user passes a GitHub issue number or URL, fetch it with `gh issue view \u003Cnumber>` (with comments). If a NOUS plan file exists at `.nous\u002Fplans\u002F\u003Cdomain>-plan.md` or `docs\u002Fnous\u002Fplans\u002F\u003Cdomain>-plan.md`, read it.\n\n### 2. Explore the codebase (optional)\n\nIf you have not already explored the codebase, do so to understand current state.\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 (schema, API, UI, tests), NOT a horizontal slice of one layer.\n\nSlices may be **HITL** or **AFK**:\n\n- **HITL** — Human In The Loop. Requires architectural decision, design review, or judgment call.\n- **AFK** — Away From Keyboard. Can be implemented and merged without human interaction.\n\nPrefer 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 has them)\n\nAsk:\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 HITL vs AFK?\n\nIterate until the user approves the breakdown.\n\n### 5. Create the GitHub issues\n\nFor each approved slice, create a GitHub issue with `gh issue create`. Use the body template below.\n\nCreate issues **in dependency order** (blockers first) so you can reference real issue numbers in the \"Blocked by\" field.\n\n## Issue template\n\n```md\n## Parent\n\n#\u003Cparent-issue-number> (omit this section if there is no parent)\n\n## What to build\n\nConcise description of this vertical slice. Describe end-to-end behavior, not layer-by-layer implementation.\n\n## Acceptance criteria\n\n- [ ] Criterion 1\n- [ ] Criterion 2\n- [ ] Criterion 3\n\n## Blocked by\n\n- Blocked by #\u003Cissue-number> (if any)\n\nOr \"None — can start immediately\" if no blockers.\n```\n\n## Rules\n\n- Do NOT close or modify the parent issue.\n- No file paths or line numbers in the issue body — describe behaviors and contracts.\n- Use the project's domain language (`UBIQUITOUS_LANGUAGE.md` \u002F `CONTEXT.md` if present).\n- After filing, print all issue URLs with blocking relationships summarized.\n",{"name":5,"risk":35,"type":22,"version":36,"description":7},"medium","0.1.0","main","05ddbcce9e3471b880e9edc7c63e4bdd40359861","skills\u002Fto-issues","https:\u002F\u002Fgithub.com\u002Fmax-kharena\u002Fnous","https:\u002F\u002Fgithub.com\u002Fmax-kharena","2026-04-28 22:54:20",{"source":8,"skillName":5,"commands":44,"prompt":54,"zipAvailable":55},[45,48,51],{"tool":46,"command":47},"npx","npx skills add max-kharena\u002Fnous --skill to-issues",{"tool":49,"command":50},"bunx","bunx skills add max-kharena\u002Fnous --skill to-issues",{"tool":52,"command":53},"pnpm","pnpm dlx skills add max-kharena\u002Fnous --skill to-issues","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmax-kharena\u002Fnous\u002Fblob\u002Fmain\u002Fskills\u002Fto-issues\u002FSKILL.md",true,[],[58,84,106,121,143,161],{"skillNo":59,"name":60,"nameZh":6,"description":61,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":62,"categories":63,"keywords":69,"publishedAt":30},"01M71NSZ170Z45TAP4CWY74YH3","write-a-skill","Create new agent skills with proper structure, progressive disclosure, and bundled resources. Use when the user wants to create, write, or build a new skill.","https:\u002F\u002Fgithub.com\u002Fmax-kharena\u002Fnous\u002Fblob\u002Fmain\u002Fskills\u002Fwrite-a-skill\u002FSKILL.md",[64],{"categoryNo":65,"categoryName":66,"taxonomyType":67,"taxonomyTypeDesc":68},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[70,71,72,73,74,75,76,77,29,78,79,80,81,25,26,82,83],"write a skill","write","a skill","create","structure","build","new skill","with","new agent","resources","progressive","new","progressive disclosure","Meta",{"skillNo":85,"name":86,"nameZh":6,"description":87,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":88,"categories":89,"keywords":95,"publishedAt":30},"01M71NSX1D1C2MK3NJ42E1GQ47","verification-before-completion","Use when about to claim work is complete, fixed, passing, ready, merged, shippable, reviewed, or verified.","https:\u002F\u002Fgithub.com\u002Fmax-kharena\u002Fnous\u002Fblob\u002Fmain\u002Fskills\u002Fverification-before-completion\u002FSKILL.md",[90],{"categoryNo":91,"categoryName":92,"taxonomyType":93,"taxonomyTypeDesc":94},"01JBSEEDCAT000000000000037","律师与法务","PROFESSION","适用职业",[96,97,25,26,98,99,100,101,102,103,104,105],"verification","verification before completion","verified","claim","complete","quality","about","high","work","ready",{"skillNo":107,"name":108,"nameZh":6,"description":109,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":110,"categories":111,"keywords":112,"publishedAt":30},"01M71NSVRTWNA5RYBRRRBQ4830","using-nous","Use when a request needs NOUS command routing or personality-driven planning.","https:\u002F\u002Fgithub.com\u002Fmax-kharena\u002Fnous\u002Fblob\u002Fmain\u002Fskills\u002Fusing-nous\u002FSKILL.md",[],[113,114,115,26,25,116,117,22,118,119,120],"using nous","personality","driven","command routing","request","command","routing","router",{"skillNo":122,"name":123,"nameZh":6,"description":124,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":125,"categories":126,"keywords":127,"publishedAt":30},"01M71NST398KW57VNX72Z35MC2","using-git-worktrees","Use when NOUS execution needs isolated implementation branches, phase worktrees, parallel worktrees, or safe branch setup before executing a plan.","https:\u002F\u002Fgithub.com\u002Fmax-kharena\u002Fnous\u002Fblob\u002Fmain\u002Fskills\u002Fusing-git-worktrees\u002FSKILL.md",[],[128,129,130,131,132,133,134,135,136,103,20,137,26,25,138,139,140,141,142],"git","worktrees","git worktrees","using git worktrees","Using git","execution","branch setup","implementation","safe","phase","parallel worktrees","setup","branches","branch","parallel",{"skillNo":144,"name":145,"nameZh":6,"description":146,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":147,"categories":148,"keywords":149,"publishedAt":30},"01M71NSRQ1VYJT15323W6HE1X1","ubiquitous-language","Use when the user wants to define domain terms, build a glossary, harden terminology, or extract a DDD-style ubiquitous language. Saves to UBIQUITOUS_LANGUAGE.md.","https:\u002F\u002Fgithub.com\u002Fmax-kharena\u002Fnous\u002Fblob\u002Fmain\u002Fskills\u002Fubiquitous-language\u002FSKILL.md",[],[150,151,152,153,75,154,155,156,25,29,157,158,159,26,160],"language","ubiquitous language","define","ddd","domain","style","terminology","extract","terms","harden","glossary",{"skillNo":162,"name":163,"nameZh":6,"description":164,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":165,"categories":166,"keywords":167,"publishedAt":30},"01M71NSPGTE0PY0YJ9HSDWB62B","triage-issue","Use when the user reports a bug and wants it investigated and filed as a durable GitHub issue with a TDD-based fix plan.","https:\u002F\u002Fgithub.com\u002Fmax-kharena\u002Fnous\u002Fblob\u002Fmain\u002Fskills\u002Ftriage-issue\u002FSKILL.md",[],[168,169,170,171,29,172,173,101,174,21,20,77,175,26,25,176,177],"issue","triage issue","triage","github issue","it","bug","tdd","reports","fix","as"]