[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7AE966ZXYP5SFP0Z1YFA5RT":3,"skill-same:01M7AE966ZXYP5SFP0Z1YFA5RT":45},{"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":18,"linkOnly":19,"markdownContent":20,"markdownBody":21,"frontMatter":22,"refName":23,"commitSha":24,"skillDirectory":25,"forksCount":26,"repositoryHtmlUrl":27,"repositoryHomepageUrl":28,"ownerHtmlUrl":29,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":30,"install":31,"resources":44},"01M7AE966ZXYP5SFP0Z1YFA5RT","make-plan",null,"Create a detailed, phased implementation plan with documentation discovery. Use when asked to plan a feature, task, or multi-step implementation — especially before executing with do.","HyskoaMorroh\u002Fkirara-ai","HyskoaMorroh","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F214526004?v=4","01M7AE5WPKQ7K7ZJD8QZPJ5RAW","01M7AE5WQ7CP81164FZXSMAZFJ",0,"AGPL-3.0","https:\u002F\u002Fgithub.com\u002FHyskoaMorroh\u002Fkirara-ai\u002Fblob\u002Fmain\u002Fkirara_ai\u002Fplugin_manager\u002Fbundled\u002Fskills\u002Fmake-plan\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: make-plan\ndescription: Create a detailed, phased implementation plan with documentation discovery. Use when asked to plan a feature, task, or multi-step implementation — especially before executing with do.\n---\n\n# Make Plan\n\nYou are an ORCHESTRATOR. Create an LLM-friendly plan in phases that can be executed consecutively in new chat contexts.\n\n## Delegation Model\n\nUse subagents for *fact gathering and extraction* (docs, examples, signatures, grep results). Keep *synthesis and plan authoring* with the orchestrator (phase boundaries, task framing, final wording). If a subagent report is incomplete or lacks evidence, re-check with targeted reads\u002Fgreps before finalizing.\n\n### Subagent Reporting Contract (MANDATORY)\n\nEach subagent response must include:\n1. Sources consulted (files\u002FURLs) and what was read\n2. Concrete findings (exact API names\u002Fsignatures; exact file paths\u002Flocations)\n3. Copy-ready snippet locations (example files\u002Fsections to copy)\n4. \"Confidence\" note + known gaps (what might still be missing)\n\nReject and redeploy the subagent if it reports conclusions without sources.\n\n## Plan Structure\n\n### Phase 0: Documentation Discovery (ALWAYS FIRST)\n\nBefore planning implementation, deploy \"Documentation Discovery\" subagents to:\n1. Search for and read relevant documentation, examples, and existing patterns\n2. Identify the actual APIs, methods, and signatures available (not assumed)\n3. Create a brief \"Allowed APIs\" list citing specific documentation sources\n4. Note any anti-patterns to avoid (methods that DON'T exist, deprecated parameters)\n\nThe orchestrator consolidates findings into a single Phase 0 output.\n\n### Each Implementation Phase Must Include\n\n1. **What to implement** — Frame tasks to COPY from docs, not transform existing code\n   - Good: \"Copy the V2 session pattern from docs\u002Fexamples.ts:45-60\"\n   - Bad: \"Migrate the existing code to V2\"\n2. **Documentation references** — Cite specific files\u002Flines for patterns to follow\n3. **Verification checklist** — How to prove this phase worked (tests, grep checks)\n4. **Anti-pattern guards** — What NOT to do (invented APIs, undocumented params)\n\n### Final Phase: Verification\n\n1. Verify all implementations match documentation\n2. Check for anti-patterns (grep for known bad patterns)\n3. Run tests to confirm functionality\n\n## Key Principles\n\n- Documentation Availability ≠ Usage: Explicitly require reading docs\n- Task Framing Matters: Direct agents to docs, not just outcomes\n- Verify > Assume: Require proof, not assumptions about APIs\n- Session Boundaries: Each phase should be self-contained with its own doc references\n\n## Anti-Patterns to Prevent\n\n- Inventing API methods that \"should\" exist\n- Adding parameters not in documentation\n- Skipping verification steps\n- Assuming structure without checking examples\n\n## See Also\n\n- `oh-my-issues` — the issue-side sibling. When the plan you're being asked to make is rooted in a bug or feature backlog rather than a fresh idea, route through `oh-my-issues` first to cluster issues by root cause into plan masters and `plans\u002F0X-*.md` design docs. `make-plan` then operates on the design doc for one plan slice.\n","# Make Plan\n\nYou are an ORCHESTRATOR. Create an LLM-friendly plan in phases that can be executed consecutively in new chat contexts.\n\n## Delegation Model\n\nUse subagents for *fact gathering and extraction* (docs, examples, signatures, grep results). Keep *synthesis and plan authoring* with the orchestrator (phase boundaries, task framing, final wording). If a subagent report is incomplete or lacks evidence, re-check with targeted reads\u002Fgreps before finalizing.\n\n### Subagent Reporting Contract (MANDATORY)\n\nEach subagent response must include:\n1. Sources consulted (files\u002FURLs) and what was read\n2. Concrete findings (exact API names\u002Fsignatures; exact file paths\u002Flocations)\n3. Copy-ready snippet locations (example files\u002Fsections to copy)\n4. \"Confidence\" note + known gaps (what might still be missing)\n\nReject and redeploy the subagent if it reports conclusions without sources.\n\n## Plan Structure\n\n### Phase 0: Documentation Discovery (ALWAYS FIRST)\n\nBefore planning implementation, deploy \"Documentation Discovery\" subagents to:\n1. Search for and read relevant documentation, examples, and existing patterns\n2. Identify the actual APIs, methods, and signatures available (not assumed)\n3. Create a brief \"Allowed APIs\" list citing specific documentation sources\n4. Note any anti-patterns to avoid (methods that DON'T exist, deprecated parameters)\n\nThe orchestrator consolidates findings into a single Phase 0 output.\n\n### Each Implementation Phase Must Include\n\n1. **What to implement** — Frame tasks to COPY from docs, not transform existing code\n   - Good: \"Copy the V2 session pattern from docs\u002Fexamples.ts:45-60\"\n   - Bad: \"Migrate the existing code to V2\"\n2. **Documentation references** — Cite specific files\u002Flines for patterns to follow\n3. **Verification checklist** — How to prove this phase worked (tests, grep checks)\n4. **Anti-pattern guards** — What NOT to do (invented APIs, undocumented params)\n\n### Final Phase: Verification\n\n1. Verify all implementations match documentation\n2. Check for anti-patterns (grep for known bad patterns)\n3. Run tests to confirm functionality\n\n## Key Principles\n\n- Documentation Availability ≠ Usage: Explicitly require reading docs\n- Task Framing Matters: Direct agents to docs, not just outcomes\n- Verify > Assume: Require proof, not assumptions about APIs\n- Session Boundaries: Each phase should be self-contained with its own doc references\n\n## Anti-Patterns to Prevent\n\n- Inventing API methods that \"should\" exist\n- Adding parameters not in documentation\n- Skipping verification steps\n- Assuming structure without checking examples\n\n## See Also\n\n- `oh-my-issues` — the issue-side sibling. When the plan you're being asked to make is rooted in a bug or feature backlog rather than a fresh idea, route through `oh-my-issues` first to cluster issues by root cause into plan masters and `plans\u002F0X-*.md` design docs. `make-plan` then operates on the design doc for one plan slice.\n",{"name":5,"description":7},"main","5fff0a9c53845d2db11b4e5ffe6e08fd5f18b0f6","kirara_ai\u002Fplugin_manager\u002Fbundled\u002Fskills\u002Fmake-plan",1,"https:\u002F\u002Fgithub.com\u002FHyskoaMorroh\u002Fkirara-ai","https:\u002F\u002Fkirara-docs.app.lss233.com\u002F","https:\u002F\u002Fgithub.com\u002FHyskoaMorroh","2026-11-04 21:35:01",{"source":8,"skillName":5,"commands":32,"prompt":42,"zipAvailable":43},[33,36,39],{"tool":34,"command":35},"npx","npx skills add HyskoaMorroh\u002Fkirara-ai --skill make-plan",{"tool":37,"command":38},"bunx","bunx skills add HyskoaMorroh\u002Fkirara-ai --skill make-plan",{"tool":40,"command":41},"pnpm","pnpm dlx skills add HyskoaMorroh\u002Fkirara-ai --skill make-plan","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FHyskoaMorroh\u002Fkirara-ai\u002Fblob\u002Fmain\u002Fkirara_ai\u002Fplugin_manager\u002Fbundled\u002Fskills\u002Fmake-plan\u002FSKILL.md",true,[],[46,53,60,67,74,81],{"skillNo":47,"name":48,"nameZh":6,"description":49,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":50,"categories":51,"keywords":52,"publishedAt":18},"01M7AEB5EJJD3JJHTQVFCJX4DB","writing-plans","Use when you have a spec or requirements for a multi-step task, before touching code","https:\u002F\u002Fgithub.com\u002FHyskoaMorroh\u002Fkirara-ai\u002Fblob\u002Fmain\u002Fkirara_ai\u002Fplugin_manager\u002Fbundled\u002Fskills\u002Fwriting-plans\u002FSKILL.md",[],[],{"skillNo":54,"name":55,"nameZh":6,"description":56,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":57,"categories":58,"keywords":59,"publishedAt":18},"01M7AEB3CT17MBD5BGB60AC9RA","what-the","What the? Use when the user wants a plain-English breakdown of something technical — the who, what, where, why, and when.","https:\u002F\u002Fgithub.com\u002FHyskoaMorroh\u002Fkirara-ai\u002Fblob\u002Fmain\u002Fkirara_ai\u002Fplugin_manager\u002Fbundled\u002Fskills\u002Fwhat-the\u002FSKILL.md",[],[],{"skillNo":61,"name":62,"nameZh":6,"description":63,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":64,"categories":65,"keywords":66,"publishedAt":18},"01M7AEB0G8SAHADVPA135MGNBB","verification-before-completion","Use when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always","https:\u002F\u002Fgithub.com\u002FHyskoaMorroh\u002Fkirara-ai\u002Fblob\u002Fmain\u002Fkirara_ai\u002Fplugin_manager\u002Fbundled\u002Fskills\u002Fverification-before-completion\u002FSKILL.md",[],[],{"skillNo":68,"name":69,"nameZh":6,"description":70,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":71,"categories":72,"keywords":73,"publishedAt":18},"01M7AEAVHEPZAXQTCGJ12DM6SX","using-agent-skills","Discovers and invokes agent skills. Use when starting a session or when you need to discover which skill applies to the current task. This is the meta-skill that governs how all other skills are discovered and invoked.","https:\u002F\u002Fgithub.com\u002FHyskoaMorroh\u002Fkirara-ai\u002Fblob\u002Fmain\u002Fkirara_ai\u002Fplugin_manager\u002Fbundled\u002Fskills\u002Fusing-agent-skills\u002FSKILL.md",[],[],{"skillNo":75,"name":76,"nameZh":6,"description":77,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":78,"categories":79,"keywords":80,"publishedAt":18},"01M7AEANRHNEWZQC38J5VR543M","test-driven-development","Drives development with tests. Use when implementing any logic, fixing any bug, or changing any behavior. Use when you need to prove that code works, when a bug report arrives, or when you're about to modify existing functionality.","https:\u002F\u002Fgithub.com\u002FHyskoaMorroh\u002Fkirara-ai\u002Fblob\u002Fmain\u002Fkirara_ai\u002Fplugin_manager\u002Fbundled\u002Fskills\u002Ftest-driven-development\u002FSKILL.md",[],[],{"skillNo":82,"name":83,"nameZh":6,"description":84,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":85,"categories":86,"keywords":87,"publishedAt":18},"01M7AEAH03K47FGJ7ZR5MBGBE0","spec-driven-development","Creates specs before coding. Use when starting a new project, feature, or significant change and no specification exists yet. Use when requirements are unclear, ambiguous, or only exist as a vague idea.","https:\u002F\u002Fgithub.com\u002FHyskoaMorroh\u002Fkirara-ai\u002Fblob\u002Fmain\u002Fkirara_ai\u002Fplugin_manager\u002Fbundled\u002Fskills\u002Fspec-driven-development\u002FSKILL.md",[],[]]