[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6CP1FBF4MEE0WV55KPYYP2W":3,"skill-same:01M6CP1FBF4MEE0WV55KPYYP2W":69},{"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":23,"publishedAt":43,"linkOnly":44,"markdownContent":45,"markdownBody":46,"frontMatter":47,"refName":48,"commitSha":49,"skillDirectory":50,"forksCount":51,"repositoryHtmlUrl":52,"repositoryHomepageUrl":6,"ownerHtmlUrl":53,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":54,"install":55,"resources":68},"01M6CP1FBF4MEE0WV55KPYYP2W","brainstorming",null,"Coordinates collaborative design sessions that explore requirements, analyze codebase context, and produce an approved design document with trade-offs. Use when building a new feature, adding functionality, creating components, modifying behavior, starting a project, or planning any creative work. DO NOT TRIGGER when the user already has a concrete design and just wants implementation.","shousper\u002Fclanker-kit","shousper","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F1144345?v=4","01M6CP153W30NV9J1XT8K98G4J","Corey McGregor","01M6CP157WFP2WEFX4TJH7JVPG",5,"MIT","https:\u002F\u002Fgithub.com\u002Fshousper\u002Fclanker-kit\u002Fblob\u002Fmain\u002Fshared\u002Fskills\u002Fbrainstorming\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000015","视觉设计","SCENARIO","使用场景",[5,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42],"context","coordinates","do","document","implementation","creative","use","new feature","user","behavior","design","work","just","analyze","explore","produce","planning","sessions","components","2026-11-10 10:12:30",false,"---\nname: brainstorming\ndescription: Coordinates collaborative design sessions that explore requirements, analyze codebase context, and produce an approved design document with trade-offs. Use when building a new feature, adding functionality, creating components, modifying behavior, starting a project, or planning any creative work. DO NOT TRIGGER when the user already has a concrete design and just wants implementation.\n---\n\n# Brainstorming Ideas Into Designs\n\n## Overview\n\nHelp turn ideas into fully formed designs through collaborative dialogue, enhanced by parallel research scouts.\n\nDeploy scouts to explore project context in parallel, synthesize their findings, then ask questions one at a time to refine the idea. Once you understand what you're building, present the design and get user approval.\n\n\u003CHARD-GATE>\nDo NOT invoke any implementation skill, write any code, scaffold any project, or take any implementation action until you have presented a design and your human partner has approved it. This applies to EVERY project regardless of perceived simplicity.\n\u003C\u002FHARD-GATE>\n\n## Anti-Pattern: \"This Is Too Simple To Need A Design\"\n\nEvery project goes through this process. \"Simple\" projects are where unexamined assumptions cause the most wasted work. The design can be short, but you MUST present it and get approval.\n\n## Checklist\n\nYou MUST create a task for each of these items and complete them in order:\n\n1. **Deploy research scouts** — spawn ephemeral Explore-type subagents (Agent tool, no team) to investigate project context in parallel\n2. **Synthesize findings** — collect scout reports, build understanding\n3. **Ask clarifying questions** — one at a time, understand purpose\u002Fconstraints\u002Fsuccess criteria\n4. **Propose 2-3 approaches** — with trade-offs and your recommendation\n5. **Present design** — in sections scaled to their complexity, ask after each section whether it looks right so far\n6. **Get explicit design approval** — STOP and wait for your human partner to confirm the design. Do NOT proceed until they explicitly approve. If they have concerns, revise and re-present.\n7. **Create worktree** — on design approval, invoke kit:git-worktrees to create isolated workspace and cd into it\n8. **Write design doc** — save to `docs\u002Fplans\u002FYYYY-MM-DD-\u003Ctopic>-design.md` in the worktree (do NOT commit)\n9. **STOP — confirm transition** — Tell your human partner the design is documented and ask if they're ready to move to implementation planning. Do NOT invoke writing-plans until they confirm.\n10. **Invoke writing-plans** — on confirmation, invoke kit:writing-plans to create the implementation plan\n\n## Re-Entry (Same Worktree)\n\nWhen brainstorming is re-invoked after implementation feedback (already in a worktree):\n\n**Detection:**\n```bash\n# Check if we're in a worktree (not the main working tree)\ngit worktree list --porcelain | grep -A2 \"$(pwd)\"\n```\n\nIf already in a worktree:\n- **Skip** scout phase (codebase context already established)\n- **Skip** worktree creation (already in one)\n- Go straight to dialogue with the existing design doc as context\n- Read existing `docs\u002Fplans\u002F*-design.md` to understand prior design decisions\n- If multiple design docs exist, read the most recent one (latest date prefix)\n- Write updated\u002Fnew design doc to same `docs\u002Fplans\u002F` directory\n\n## Process Flow\n\n```dot\ndigraph brainstorming {\n    \"Already in worktree?\" [shape=diamond];\n    \"Spawn ephemeral scouts\" [shape=box];\n    \"Scouts explore in parallel\" [shape=box];\n    \"Synthesize scout findings\" [shape=box];\n    \"Ask clarifying questions\" [shape=box];\n    \"Propose 2-3 approaches\" [shape=box];\n    \"Present design sections\" [shape=box];\n    \"STOP — wait for explicit approval\" [shape=doubleoctagon, style=bold];\n    \"User approves design?\" [shape=diamond];\n    \"Create worktree (kit:git-worktrees)\" [shape=box];\n    \"Write design doc (no commit)\" [shape=box];\n    \"STOP — confirm transition\" [shape=doubleoctagon, style=bold];\n    \"Ready for implementation?\" [shape=diamond];\n    \"Invoke writing-plans skill\" [shape=doublecircle];\n\n    \"Already in worktree?\" -> \"Ask clarifying questions\" [label=\"yes — skip scouts\"];\n    \"Already in worktree?\" -> \"Spawn ephemeral scouts\" [label=\"no — fresh start\"];\n    \"Spawn ephemeral scouts\" -> \"Scouts explore in parallel\";\n    \"Scouts explore in parallel\" -> \"Synthesize scout findings\";\n    \"Synthesize scout findings\" -> \"Ask clarifying questions\";\n    \"Ask clarifying questions\" -> \"Propose 2-3 approaches\";\n    \"Propose 2-3 approaches\" -> \"Present design sections\";\n    \"Present design sections\" -> \"STOP — wait for explicit approval\";\n    \"STOP — wait for explicit approval\" -> \"User approves design?\";\n    \"User approves design?\" -> \"Present design sections\" [label=\"no, revise\"];\n    \"User approves design?\" -> \"Create worktree (kit:git-worktrees)\" [label=\"yes (fresh start)\"];\n    \"User approves design?\" -> \"Write design doc (no commit)\" [label=\"yes (re-entry)\"];\n    \"Create worktree (kit:git-worktrees)\" -> \"Write design doc (no commit)\";\n    \"Write design doc (no commit)\" -> \"STOP — confirm transition\";\n    \"STOP — confirm transition\" -> \"Ready for implementation?\";\n    \"Ready for implementation?\" -> \"Invoke writing-plans skill\" [label=\"yes\"];\n}\n```\n\n**The terminal state is invoking writing-plans.** Do NOT invoke any other implementation skill.\n\n## Research Scout Phase\n\n**REQUIRED (fresh start only):** Spawn ephemeral Explore-type subagents via the Agent tool — no team, no shutdown.\n\n### 1. Spawn Scouts\n\nSpawn 2-3 ephemeral Explore-type subagents (Agent tool, no team) to investigate different aspects in parallel:\n\n- **scout-codebase** (Explore): Explore codebase structure, key patterns, relevant files\n- **scout-docs** (Explore): Read docs, README, recent commits related to topic\n- **scout-patterns** (Explore): Find similar implementations or patterns in the codebase\n\nSpawn all scouts in a single message for maximum parallelism. For a large or highly varied sweep, author a dynamic scout workflow instead. Scouts are ephemeral — they end when they return their reports; there is no team to shut down.\n\n### 2. Synthesize\n\nCollect all scout reports. Build comprehensive understanding before engaging your human partner.\n\n## The Dialogue\n\n**Understanding the idea:**\n- Present synthesized context to your human partner (or existing design context on re-entry)\n- Ask questions one at a time to refine the idea\n- Prefer multiple choice questions when possible\n- Only one question per message\n- Focus on: purpose, constraints, success criteria\n\n**Exploring approaches:**\n- Propose 2-3 approaches with trade-offs\n- Lead with your recommended option\n- Optionally spawn approach-elaboration teammates for parallel deep-dives\n\n**Presenting the design:**\n- Once you believe you understand what you're building, present the design\n- Scale each section to its complexity: a few sentences if straightforward, up to 200-300 words if nuanced\n- Ask after each section whether it looks right so far\n- Cover: architecture, components, data flow, error handling, testing\n- Be ready to go back and clarify if something doesn't make sense\n\n\u003CHARD-GATE>\nAfter presenting the design, STOP and wait for your human partner to explicitly approve it. Do NOT write the design doc, create a worktree, or invoke any other skill until they confirm. \"Looks good\", \"approved\", \"let's go\" = proceed. Anything else = revise and re-present.\n\u003C\u002FHARD-GATE>\n\n## After the Design (only after explicit approval)\n\n**Worktree (fresh start only):**\n- Invoke kit:git-worktrees to create worktree and cd into it\n- Branch name: Derive from topic using kebab-case with a feature\u002F prefix (e.g., feature\u002Fauth-system)\n- This is the moment isolation begins\n\n**Documentation:**\n- Write validated design to `docs\u002Fplans\u002FYYYY-MM-DD-\u003Ctopic>-design.md`\n- Do NOT commit the design document\n\n\u003CHARD-GATE>\nAfter writing the design doc, STOP and ask your human partner if they are ready to proceed to implementation planning. Do NOT invoke writing-plans until they confirm. They may want to review the design doc, make changes, or take a break before continuing.\n\u003C\u002FHARD-GATE>\n\n**Implementation (only after human confirms):**\n- Invoke the writing-plans skill to create implementation plan\n- Do NOT invoke any other skill. writing-plans is the next step.\n\n## Key Principles\n\n- **One question at a time** — don't overwhelm\n- **Multiple choice preferred** — easier to answer\n- **YAGNI ruthlessly** — remove unnecessary features\n- **Explore alternatives** — always propose 2-3 approaches\n- **Incremental validation** — get approval before moving on\n- **Scouts enhance, don't replace dialogue** — human conversation is the core\n- **No commits** — design docs are workspace artifacts, not git artifacts\n","# Brainstorming Ideas Into Designs\n\n## Overview\n\nHelp turn ideas into fully formed designs through collaborative dialogue, enhanced by parallel research scouts.\n\nDeploy scouts to explore project context in parallel, synthesize their findings, then ask questions one at a time to refine the idea. Once you understand what you're building, present the design and get user approval.\n\n\u003CHARD-GATE>\nDo NOT invoke any implementation skill, write any code, scaffold any project, or take any implementation action until you have presented a design and your human partner has approved it. This applies to EVERY project regardless of perceived simplicity.\n\u003C\u002FHARD-GATE>\n\n## Anti-Pattern: \"This Is Too Simple To Need A Design\"\n\nEvery project goes through this process. \"Simple\" projects are where unexamined assumptions cause the most wasted work. The design can be short, but you MUST present it and get approval.\n\n## Checklist\n\nYou MUST create a task for each of these items and complete them in order:\n\n1. **Deploy research scouts** — spawn ephemeral Explore-type subagents (Agent tool, no team) to investigate project context in parallel\n2. **Synthesize findings** — collect scout reports, build understanding\n3. **Ask clarifying questions** — one at a time, understand purpose\u002Fconstraints\u002Fsuccess criteria\n4. **Propose 2-3 approaches** — with trade-offs and your recommendation\n5. **Present design** — in sections scaled to their complexity, ask after each section whether it looks right so far\n6. **Get explicit design approval** — STOP and wait for your human partner to confirm the design. Do NOT proceed until they explicitly approve. If they have concerns, revise and re-present.\n7. **Create worktree** — on design approval, invoke kit:git-worktrees to create isolated workspace and cd into it\n8. **Write design doc** — save to `docs\u002Fplans\u002FYYYY-MM-DD-\u003Ctopic>-design.md` in the worktree (do NOT commit)\n9. **STOP — confirm transition** — Tell your human partner the design is documented and ask if they're ready to move to implementation planning. Do NOT invoke writing-plans until they confirm.\n10. **Invoke writing-plans** — on confirmation, invoke kit:writing-plans to create the implementation plan\n\n## Re-Entry (Same Worktree)\n\nWhen brainstorming is re-invoked after implementation feedback (already in a worktree):\n\n**Detection:**\n```bash\n# Check if we're in a worktree (not the main working tree)\ngit worktree list --porcelain | grep -A2 \"$(pwd)\"\n```\n\nIf already in a worktree:\n- **Skip** scout phase (codebase context already established)\n- **Skip** worktree creation (already in one)\n- Go straight to dialogue with the existing design doc as context\n- Read existing `docs\u002Fplans\u002F*-design.md` to understand prior design decisions\n- If multiple design docs exist, read the most recent one (latest date prefix)\n- Write updated\u002Fnew design doc to same `docs\u002Fplans\u002F` directory\n\n## Process Flow\n\n```dot\ndigraph brainstorming {\n    \"Already in worktree?\" [shape=diamond];\n    \"Spawn ephemeral scouts\" [shape=box];\n    \"Scouts explore in parallel\" [shape=box];\n    \"Synthesize scout findings\" [shape=box];\n    \"Ask clarifying questions\" [shape=box];\n    \"Propose 2-3 approaches\" [shape=box];\n    \"Present design sections\" [shape=box];\n    \"STOP — wait for explicit approval\" [shape=doubleoctagon, style=bold];\n    \"User approves design?\" [shape=diamond];\n    \"Create worktree (kit:git-worktrees)\" [shape=box];\n    \"Write design doc (no commit)\" [shape=box];\n    \"STOP — confirm transition\" [shape=doubleoctagon, style=bold];\n    \"Ready for implementation?\" [shape=diamond];\n    \"Invoke writing-plans skill\" [shape=doublecircle];\n\n    \"Already in worktree?\" -> \"Ask clarifying questions\" [label=\"yes — skip scouts\"];\n    \"Already in worktree?\" -> \"Spawn ephemeral scouts\" [label=\"no — fresh start\"];\n    \"Spawn ephemeral scouts\" -> \"Scouts explore in parallel\";\n    \"Scouts explore in parallel\" -> \"Synthesize scout findings\";\n    \"Synthesize scout findings\" -> \"Ask clarifying questions\";\n    \"Ask clarifying questions\" -> \"Propose 2-3 approaches\";\n    \"Propose 2-3 approaches\" -> \"Present design sections\";\n    \"Present design sections\" -> \"STOP — wait for explicit approval\";\n    \"STOP — wait for explicit approval\" -> \"User approves design?\";\n    \"User approves design?\" -> \"Present design sections\" [label=\"no, revise\"];\n    \"User approves design?\" -> \"Create worktree (kit:git-worktrees)\" [label=\"yes (fresh start)\"];\n    \"User approves design?\" -> \"Write design doc (no commit)\" [label=\"yes (re-entry)\"];\n    \"Create worktree (kit:git-worktrees)\" -> \"Write design doc (no commit)\";\n    \"Write design doc (no commit)\" -> \"STOP — confirm transition\";\n    \"STOP — confirm transition\" -> \"Ready for implementation?\";\n    \"Ready for implementation?\" -> \"Invoke writing-plans skill\" [label=\"yes\"];\n}\n```\n\n**The terminal state is invoking writing-plans.** Do NOT invoke any other implementation skill.\n\n## Research Scout Phase\n\n**REQUIRED (fresh start only):** Spawn ephemeral Explore-type subagents via the Agent tool — no team, no shutdown.\n\n### 1. Spawn Scouts\n\nSpawn 2-3 ephemeral Explore-type subagents (Agent tool, no team) to investigate different aspects in parallel:\n\n- **scout-codebase** (Explore): Explore codebase structure, key patterns, relevant files\n- **scout-docs** (Explore): Read docs, README, recent commits related to topic\n- **scout-patterns** (Explore): Find similar implementations or patterns in the codebase\n\nSpawn all scouts in a single message for maximum parallelism. For a large or highly varied sweep, author a dynamic scout workflow instead. Scouts are ephemeral — they end when they return their reports; there is no team to shut down.\n\n### 2. Synthesize\n\nCollect all scout reports. Build comprehensive understanding before engaging your human partner.\n\n## The Dialogue\n\n**Understanding the idea:**\n- Present synthesized context to your human partner (or existing design context on re-entry)\n- Ask questions one at a time to refine the idea\n- Prefer multiple choice questions when possible\n- Only one question per message\n- Focus on: purpose, constraints, success criteria\n\n**Exploring approaches:**\n- Propose 2-3 approaches with trade-offs\n- Lead with your recommended option\n- Optionally spawn approach-elaboration teammates for parallel deep-dives\n\n**Presenting the design:**\n- Once you believe you understand what you're building, present the design\n- Scale each section to its complexity: a few sentences if straightforward, up to 200-300 words if nuanced\n- Ask after each section whether it looks right so far\n- Cover: architecture, components, data flow, error handling, testing\n- Be ready to go back and clarify if something doesn't make sense\n\n\u003CHARD-GATE>\nAfter presenting the design, STOP and wait for your human partner to explicitly approve it. Do NOT write the design doc, create a worktree, or invoke any other skill until they confirm. \"Looks good\", \"approved\", \"let's go\" = proceed. Anything else = revise and re-present.\n\u003C\u002FHARD-GATE>\n\n## After the Design (only after explicit approval)\n\n**Worktree (fresh start only):**\n- Invoke kit:git-worktrees to create worktree and cd into it\n- Branch name: Derive from topic using kebab-case with a feature\u002F prefix (e.g., feature\u002Fauth-system)\n- This is the moment isolation begins\n\n**Documentation:**\n- Write validated design to `docs\u002Fplans\u002FYYYY-MM-DD-\u003Ctopic>-design.md`\n- Do NOT commit the design document\n\n\u003CHARD-GATE>\nAfter writing the design doc, STOP and ask your human partner if they are ready to proceed to implementation planning. Do NOT invoke writing-plans until they confirm. They may want to review the design doc, make changes, or take a break before continuing.\n\u003C\u002FHARD-GATE>\n\n**Implementation (only after human confirms):**\n- Invoke the writing-plans skill to create implementation plan\n- Do NOT invoke any other skill. writing-plans is the next step.\n\n## Key Principles\n\n- **One question at a time** — don't overwhelm\n- **Multiple choice preferred** — easier to answer\n- **YAGNI ruthlessly** — remove unnecessary features\n- **Explore alternatives** — always propose 2-3 approaches\n- **Incremental validation** — get approval before moving on\n- **Scouts enhance, don't replace dialogue** — human conversation is the core\n- **No commits** — design docs are workspace artifacts, not git artifacts\n",{"name":5,"description":7},"main","ffcb87b7a18526a98eccab20c8c12526bb10af96","shared\u002Fskills\u002Fbrainstorming",2,"https:\u002F\u002Fgithub.com\u002Fshousper\u002Fclanker-kit","https:\u002F\u002Fgithub.com\u002Fshousper","2026-10-27 23:43:43",{"source":8,"skillName":5,"commands":56,"prompt":66,"zipAvailable":67},[57,60,63],{"tool":58,"command":59},"npx","npx skills add shousper\u002Fclanker-kit --skill brainstorming",{"tool":61,"command":62},"bunx","bunx skills add shousper\u002Fclanker-kit --skill brainstorming",{"tool":64,"command":65},"pnpm","pnpm dlx skills add shousper\u002Fclanker-kit --skill brainstorming","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fshousper\u002Fclanker-kit\u002Fblob\u002Fmain\u002Fshared\u002Fskills\u002Fbrainstorming\u002FSKILL.md",true,[],[70,103,127,143,163,175],{"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":87,"publishedAt":43},"01M6CP3FKPXFKQBY5979X2W9GN","writing-docs","Use when creating or editing documentation of any kind, including Markdown, RST, or HTML pages, READMEs, design docs, ADRs, changelogs, docstrings, and comment blocks. Covers document purpose, headings, paragraphs, lists, procedures, notices, cross-references, code samples, placeholders, example data, and word choice for technical writing.","https:\u002F\u002Fgithub.com\u002Fshousper\u002Fclanker-kit\u002Fblob\u002Fmain\u002Fshared\u002Fwriting\u002Fskills\u002Fwriting-docs\u002FSKILL.md",[76,79,82],{"categoryNo":77,"categoryName":78,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000002","文档处理",{"categoryNo":80,"categoryName":81,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000018","写作与文案",{"categoryNo":83,"categoryName":84,"taxonomyType":85,"taxonomyTypeDesc":86},"01JBSEEDCAT000000000000036","内容创作者","PROFESSION","适用职业",[88,89,90,34,91,92,93,94,95,96,97,98,99,30,100,101,27,102],"writing","docs","writing docs","technical writing","documentation","code","data","markdown","Word","choice","editing","technical","html","example","references",{"skillNo":104,"name":35,"nameZh":6,"description":105,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":106,"categories":107,"keywords":108,"publishedAt":43},"01M6CP3CHHC5S3FG5DS38W6PP8","Runs the story worker loop in a story-workflow project — claim ready stories, implement each in its own worktree, close through verification gates, repeat until the goal is met or the loop stalls. Use when asked to \"work the board\", \"complete all stories\", \"work on epic st-XXXX\", \"pick up the next story\", \"start a worker\", or to resume or continue a story run — and when a loop re-prompt names the next story in a session that started the loop. DO NOT TRIGGER without .agents\u002Fshousper-stories\u002Fconfig.json (use stories:setup first), for decomposing a spec into stories (stories:plan), or to stop a run (stories:cancel).","https:\u002F\u002Fgithub.com\u002Fshousper\u002Fclanker-kit\u002Fblob\u002Fmain\u002Fshared\u002Fstories\u002Fskills\u002Fwork\u002FSKILL.md",[],[35,109,110,111,112,113,114,115,116,117,118,119,120,121,122,123,124,26,125,126],"workflow","config","run","verification","worktree","start","loop","plan","work on","pick","verification gates","session","ready","up","goal","stop","claim","next",{"skillNo":128,"name":129,"nameZh":6,"description":130,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":131,"categories":132,"keywords":133,"publishedAt":43},"01M6CP39QNRN136HV0F62TMS7P","using-stories","Compressed story-workflow rulebook, injected automatically at session start (including after compaction) in projects with .agents\u002Fshousper-stories\u002Fconfig.json. Use when unsure of the workflow rules mid-session, when asked \"how does the story workflow work here\", or for a story CLI quick reference. DO NOT TRIGGER in projects without .agents\u002Fshousper-stories\u002Fconfig.json, to set up the workflow (stories:setup), to file stories (stories:plan), or to run the loop (stories:work).","https:\u002F\u002Fgithub.com\u002Fshousper\u002Fclanker-kit\u002Fblob\u002Fmain\u002Fshared\u002Fstories\u002Fskills\u002Fusing-stories\u002FSKILL.md",[],[134,135,109,110,136,111,114,137,138,115,116,139,140,141,35,120,30,122,142,26],"using stories","cli","quick reference","SET","how","projects","json","Rules","reference",{"skillNo":144,"name":145,"nameZh":6,"description":146,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":147,"categories":148,"keywords":152,"publishedAt":43},"01M6CP36Y3D5S74HQQX62D6SMC","setup","Interactive onboarding that turns a repo into a story-workflow project — merge-mode choice, verification gates with test-runner detection, gitignore wiring, optional project-specific reviewer personas. Use when asked to \"set up the story workflow\", \"adopt stories\", \"story init\", \"install the story board\", or when stories:plan \u002F stories:work is wanted but .agents\u002Fshousper-stories\u002Fconfig.json does not exist yet. DO NOT TRIGGER when .agents\u002Fshousper-stories\u002Fconfig.json already exists (use stories:plan to file work, stories:work to execute it), for creating individual stories, or for project scaffolding unrelated to the story workflow.","https:\u002F\u002Fgithub.com\u002Fshousper\u002Fclanker-kit\u002Fblob\u002Fmain\u002Fshared\u002Fstories\u002Fskills\u002Fsetup\u002FSKILL.md",[149],{"categoryNo":150,"categoryName":151,"taxonomyType":85,"taxonomyTypeDesc":86},"01JBSEEDCAT000000000000038","人力资源",[145,109,153,154,112,155,137,97,156,35,157,119,158,30,122,26,159,160,161,162],"test","init","file","reviewer","repo","interactive","personas","runner","gitignore","test-runner",{"skillNo":164,"name":116,"nameZh":6,"description":165,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":166,"categories":167,"keywords":168,"publishedAt":43},"01M6CP33ZJE0SNZAK43Z5RGPDQ","Decomposes a spec or approved design into epics and stories on the story board — sized, dependency-ordered, gated, human-approved, then filed via the story CLI. Use in a project with .agents\u002Fshousper-stories\u002Fconfig.json when there is a design doc (often from kit:brainstorming), spec, requirements file, or feature request to break down; it replaces kit:writing-plans in the workflow chain for story-based projects. Also use for \"file stories\", \"break this into stories\", \"populate the board\". DO NOT TRIGGER in projects without .agents\u002Fshousper-stories\u002Fconfig.json (use kit:writing-plans), for executing stories (stories:work), or for filing a single discovered-work story mid-loop (plain story create).","https:\u002F\u002Fgithub.com\u002Fshousper\u002Fclanker-kit\u002Fblob\u002Fmain\u002Fshared\u002Fstories\u002Fskills\u002Fplan\u002FSKILL.md",[],[116,34,88,135,169,109,110,5,170,155,115,139,140,171,35,172,30,173,26,174],"spec","create","design doc","board","dependency","gated",{"skillNo":176,"name":177,"nameZh":6,"description":178,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":179,"categories":180,"keywords":181,"publishedAt":43},"01M6CP31SH1DH78VYHRKEW8HK7","cancel","Stops an active story loop and reports where the board stands. Use when asked to \"stop the loop\", \"cancel the story run\", \"halt autonomous story work\", \"kill the worker loop\", or when a runaway run must be shut down. DO NOT TRIGGER for closing a single story (that is story done inside stories:work), for deleting or archiving stories, or for removing the story workflow from a project.","https:\u002F\u002Fgithub.com\u002Fshousper\u002Fclanker-kit\u002Fblob\u002Fmain\u002Fshared\u002Fstories\u002Fskills\u002Fcancel\u002FSKILL.md",[],[177,109,111,115,35,172,182,30,183,184,124,185,26,186],"autonomous","reports","Story","kill","done"]