[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7D7ERBB5Y2VCFXKSMFBB7VZ":3,"skill-same:01M7D7ERBB5Y2VCFXKSMFBB7VZ":44},{"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":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":24,"commitSha":25,"skillDirectory":26,"forksCount":14,"repositoryHtmlUrl":27,"repositoryHomepageUrl":6,"ownerHtmlUrl":28,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":29,"install":30,"resources":43},"01M7D7ERBB5Y2VCFXKSMFBB7VZ","planning",null,"Plan a focused feature, change, or technical decision within an existing project. Use when scope or implementation direction needs resolving before work begins.","qqono\u002Fpi-os","qqono","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F137879292?v=4","01M7D7EBMGW1FSSFVMV1P7CE97","bb","01M7D7EBN7KGMYJPPGJ6SA55XM",0,"MIT","https:\u002F\u002Fgithub.com\u002Fqqono\u002Fpi-os\u002Fblob\u002Fmain\u002Fskills\u002Fplanning\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: planning\ndescription: Plan a focused feature, change, or technical decision within an existing project. Use when scope or implementation direction needs resolving before work begins.\n---\n\n# Focused planning\n\nProduce the smallest plan that removes meaningful uncertainty from one bounded change.\n\n1. Read the relevant instructions, memory, glossary, ADRs, existing ticket\u002Fspec, and implementation. Verify environmental facts directly.\n2. State the user-facing problem, desired outcome, constraints, and explicit exclusions. Distinguish facts, assumptions, and decisions.\n3. If important branches remain unresolved, use the grilling discipline: work dependency-aware questions in rounds and recommend answers.\n4. Identify affected modules and their interfaces. Prefer existing seams; introduce a seam only where behavior genuinely varies. Favor deep modules that hide complexity behind a small interface.\n5. Use a throwaway prototype only when a concrete artifact will answer a named design question faster than discussion. Record the answer; do not treat prototype code as production.\n6. Define behavioral acceptance criteria, verification commands, and the highest useful test seams.\n7. Produce an ordered plan of small vertical slices. Each slice should deliver independently observable value or reduce a named risk.\n8. Confirm the plan with the user before implementation. Publish a spec or tickets only when requested or when the work cannot fit safely in one session; follow the workspace's issue-tracking guidance when present.\n\nA complete plan explains what changes, why, how success is observed, what remains unchanged, and which decisions are still open. Avoid volatile code snippets and file lists unless they are necessary to execute the immediate work.\n","# Focused planning\n\nProduce the smallest plan that removes meaningful uncertainty from one bounded change.\n\n1. Read the relevant instructions, memory, glossary, ADRs, existing ticket\u002Fspec, and implementation. Verify environmental facts directly.\n2. State the user-facing problem, desired outcome, constraints, and explicit exclusions. Distinguish facts, assumptions, and decisions.\n3. If important branches remain unresolved, use the grilling discipline: work dependency-aware questions in rounds and recommend answers.\n4. Identify affected modules and their interfaces. Prefer existing seams; introduce a seam only where behavior genuinely varies. Favor deep modules that hide complexity behind a small interface.\n5. Use a throwaway prototype only when a concrete artifact will answer a named design question faster than discussion. Record the answer; do not treat prototype code as production.\n6. Define behavioral acceptance criteria, verification commands, and the highest useful test seams.\n7. Produce an ordered plan of small vertical slices. Each slice should deliver independently observable value or reduce a named risk.\n8. Confirm the plan with the user before implementation. Publish a spec or tickets only when requested or when the work cannot fit safely in one session; follow the workspace's issue-tracking guidance when present.\n\nA complete plan explains what changes, why, how success is observed, what remains unchanged, and which decisions are still open. Avoid volatile code snippets and file lists unless they are necessary to execute the immediate work.\n",{"name":5,"description":7},"main","4ae606d378569edd0e27cd28dfbfa8f5be6b4741","skills\u002Fplanning","https:\u002F\u002Fgithub.com\u002Fqqono\u002Fpi-os","https:\u002F\u002Fgithub.com\u002Fqqono","2026-09-23 15:02:43",{"source":8,"skillName":5,"commands":31,"prompt":41,"zipAvailable":42},[32,35,38],{"tool":33,"command":34},"npx","npx skills add qqono\u002Fpi-os --skill planning",{"tool":36,"command":37},"bunx","bunx skills add qqono\u002Fpi-os --skill planning",{"tool":39,"command":40},"pnpm","pnpm dlx skills add qqono\u002Fpi-os --skill planning","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fqqono\u002Fpi-os\u002Fblob\u002Fmain\u002Fskills\u002Fplanning\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":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":49,"categories":50,"keywords":51,"publishedAt":19},"01M7D7F1K355Y53DT6K10YE907","writing-for-agents","Design or edit agent instructions, skills, prompt templates, and linked operational documents. Use when changing files whose reader is an AI agent.","https:\u002F\u002Fgithub.com\u002Fqqono\u002Fpi-os\u002Fblob\u002Fmain\u002Fskills\u002Fwriting-for-agents\u002FSKILL.md",[],[],{"skillNo":53,"name":54,"nameZh":6,"description":55,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":56,"categories":57,"keywords":58,"publishedAt":19},"01M7D7EZ9PSZT614VMEDBHK2JT","review","Review code or configuration changes against repository standards and intended requirements. Use for branches, diffs, pull requests, or work-in-progress review.","https:\u002F\u002Fgithub.com\u002Fqqono\u002Fpi-os\u002Fblob\u002Fmain\u002Fskills\u002Freview\u002FSKILL.md",[],[],{"skillNo":60,"name":61,"nameZh":6,"description":62,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":63,"categories":64,"keywords":65,"publishedAt":19},"01M7D7EX1WTYZ44091B692HENV","research","Investigate external facts, documentation, APIs, or technical options using authoritative sources. Use when a decision requires trustworthy reading beyond the workspace.","https:\u002F\u002Fgithub.com\u002Fqqono\u002Fpi-os\u002Fblob\u002Fmain\u002Fskills\u002Fresearch\u002FSKILL.md",[],[],{"skillNo":67,"name":68,"nameZh":6,"description":69,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":70,"categories":71,"keywords":72,"publishedAt":19},"01M7D7ETK0BABCFHFNZ6172V6W","project-planning","Establish, promote, restructure, or map a project or subproject. Use for new projects, inbox promotion, initial agent setup, or work too large for one session.","https:\u002F\u002Fgithub.com\u002Fqqono\u002Fpi-os\u002Fblob\u002Fmain\u002Fskills\u002Fproject-planning\u002FSKILL.md",[],[],{"skillNo":74,"name":75,"nameZh":6,"description":76,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":77,"categories":78,"keywords":79,"publishedAt":19},"01M7D7EP4CNQJWD10C7PZFQY8X","implementation","Implement an approved plan, specification, or ticket in small verified slices. Use when requirements are sufficiently settled and the user asks to build the change.","https:\u002F\u002Fgithub.com\u002Fqqono\u002Fpi-os\u002Fblob\u002Fmain\u002Fskills\u002Fimplementation\u002FSKILL.md",[],[],{"skillNo":81,"name":82,"nameZh":6,"description":83,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":84,"categories":85,"keywords":86,"publishedAt":19},"01M7D7EKVEXSP8CGQHR7KJJJ19","grilling","Stress-test a plan, decision, or idea through a rigorous interview. Use when the user asks to grill an idea or when consequential design branches remain unresolved.","https:\u002F\u002Fgithub.com\u002Fqqono\u002Fpi-os\u002Fblob\u002Fmain\u002Fskills\u002Fgrilling\u002FSKILL.md",[],[]]