[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6H6KCGAX8XSRFG6MAGVXSSN":3,"skill-same:01M6H6KCGAX8XSRFG6MAGVXSSN":65},{"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":38,"linkOnly":39,"markdownContent":40,"markdownBody":41,"frontMatter":42,"refName":43,"commitSha":44,"skillDirectory":45,"forksCount":46,"repositoryHtmlUrl":47,"repositoryHomepageUrl":6,"ownerHtmlUrl":48,"ownerBlogUrl":49,"ownerDescription":6,"updatedAt":50,"install":51,"resources":64},"01M6H6KCGAX8XSRFG6MAGVXSSN","planner",null,"Create comprehensive, phased implementation plans with sprints and atomic tasks. Use when user says: \"make a plan\", \"create a plan\", \"plan this out\", \"plan the implementation\", \"help me plan\", \"design a plan\", \"draft a plan\", \"write a plan\", \"outline the steps\", \"break this down into tasks\", \"what's the plan for\", or any similar planning request. Also triggers on explicit \"\u002Fplanner\" or \"\u002Fplan\" commands.","0xharryriddle\u002Fcodex-field-kit","0xharryriddle","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F100945007?v=4","01M6H686JV0QKZYP2RWG6B2B8T","harryriddle","01M6H686PVZ8JGKWEG7B3GM5PD",3,"MIT","https:\u002F\u002Fgithub.com\u002F0xharryriddle\u002Fcodex-field-kit\u002Fblob\u002Fmain\u002Farchive\u002Fupstream\u002Fexamples\u002Fskills\u002Fplanner\u002FSKILL.md",[],[5,19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37],"me","for","atomic","with","sprints","triggers","plans","commands","outline","draft","design","use","write","phased implementation","plan","help","planning","create","tasks","2026-11-10 10:12:30",false,"---\nname: planner\ndescription: >\n  Create comprehensive, phased implementation plans with sprints and atomic tasks.\n  Use when user says: \"make a plan\", \"create a plan\", \"plan this out\", \"plan the implementation\",\n  \"help me plan\", \"design a plan\", \"draft a plan\", \"write a plan\", \"outline the steps\",\n  \"break this down into tasks\", \"what's the plan for\", or any similar planning request.\n  Also triggers on explicit \"\u002Fplanner\" or \"\u002Fplan\" commands.\n---\n\n# Planner Agent\n\nCreate detailed, phased implementation plans for bugs, features, or tasks.\n\n## Process\n\n### Phase 0: Research\n\n1. **Investigate the codebase:**\n   - Architecture and patterns\n   - Similar existing implementations\n   - Dependencies and frameworks\n   - Related components\n\n2. **Analyze the request:**\n   - Core requirements\n   - Challenges & edge cases\n   - Security\u002Fperformance\u002FUX considerations\n\n### Phase 1: Clarify Requirements\n\nBefore doing ANY documentation search: clarify requirements with user.\nThis will narrow and aid you in finding the right docs.\n\nThink of 5-10 questions that will help you generate the best plan possible.\n\nHere are suggested example categories, but not a strict or exhaustive list. You may ask anything helpful. Use best judgement & prioritize ambiguity and risk reduction:\n1. Goals & success criteria\n2. Scope & non‑goals\n3. Users & core workflows\n4. Platforms & environments\n5. Tech constraints\n6. Data & integrations\n7. Auth & permissions\n8. Performance & reliability\n9. Testing & validation\n10. Ask any helpful question\n\n### Phase 2: Retrieve Documentation\n\nWhen the plan involves any external library, API, framework, or service, use the Context7 skill to fetch the latest official docs before drafting tasks. This ensures version‑accurate steps, correct parameters, and current best practices. If no external dependencies apply, skip this phase.\n\n### Phase 3: Create Plan\n\n#### Structure\n- **Overview**: Brief summary and approach\n- **Sprints**: Logical phases that build on each other\n- **Tasks**: Specific, actionable items within sprints\n\n#### Sprint Requirements\nEach sprint must:\n- Result in **demoable, runnable, testable** increment\n- Build on prior sprint work\n- Include demo\u002Fverification checklist\n\n#### Task Requirements\nEach task must be:\n- **Atomic and committable** (small, independent)\n- Specific with clear inputs\u002Foutputs\n- Independently testable\n- Include file paths when relevant\n- Include dependencies for parallel execution\n- Include tests or validation method\n\n**Bad:** \"Implement Google OAuth\"\n**Good:**\n- \"Add Google OAuth config to env variables\"\n- \"Install passport-google-oauth20 package\"\n- \"Create OAuth callback route in src\u002Froutes\u002Fauth.ts\"\n- \"Add Google sign-in button to login UI\"\n\n### Phase 3: Save\nSave the file\n\nGenerate filename from request:\n1. Extract keywords\n2. Convert to kebab-case\n3. Add `-plan.md` suffix\n\nExamples:\n- \"fix xyz bug\" → `xyz-bug-plan.md`\n\n### Phase 4: Gotchas\n\nAFTER it is saved. Identify potential issues & edge cases in plan. Address proactively. Where could smth go wrong? What about the plan is ambiguous? Missing step, dependency, or pitfall?\n\nIf any gotchas found, stop & ask up to 3 more questions. (either w\u002F request_user_input or directly)\n\nRefine the plan if any additional useful info is provided.\n\n## Plan Template\n\n```markdown\n# Plan: [Task Name]\n\n**Generated**: [Date]\n**Estimated Complexity**: [Low\u002FMedium\u002FHigh]\n\n## Overview\n[Summary of task and approach]\n\n## Prerequisites\n- [Dependencies or requirements]\n- [Tools, libraries, access needed]\n\n## Sprint 1: [Name]\n**Goal**: [What this accomplishes]\n**Demo\u002FValidation**:\n- [How to run\u002Fdemo]\n- [What to verify]\n\n### Task 1.1: [Name]\n- **Location**: [File paths]\n- **Description**: [What to do]\n- **Dependencies**: [Previous tasks]\n- **Acceptance Criteria**:\n  - [Specific criteria]\n- **Validation**:\n  - [Tests or verification]\n\n### Task 1.2: [Name]\n[...]\n\n## Sprint 2: [Name]\n[...]\n\n## Testing Strategy\n- [How to test]\n- [What to verify per sprint]\n\n## Potential Risks & Gotchas\n- [What could go wrong]\n- [Mitigation strategies]\n\n## Rollback Plan\n- [How to undo if needed]\n```\n\n## Important\n\n- Think about full lifecycle: implementation, testing, deployment\n- Consider non-functional requirements\n- Show user summary and file path when done\n- Do NOT implement - only create the plan\n","# Planner Agent\n\nCreate detailed, phased implementation plans for bugs, features, or tasks.\n\n## Process\n\n### Phase 0: Research\n\n1. **Investigate the codebase:**\n   - Architecture and patterns\n   - Similar existing implementations\n   - Dependencies and frameworks\n   - Related components\n\n2. **Analyze the request:**\n   - Core requirements\n   - Challenges & edge cases\n   - Security\u002Fperformance\u002FUX considerations\n\n### Phase 1: Clarify Requirements\n\nBefore doing ANY documentation search: clarify requirements with user.\nThis will narrow and aid you in finding the right docs.\n\nThink of 5-10 questions that will help you generate the best plan possible.\n\nHere are suggested example categories, but not a strict or exhaustive list. You may ask anything helpful. Use best judgement & prioritize ambiguity and risk reduction:\n1. Goals & success criteria\n2. Scope & non‑goals\n3. Users & core workflows\n4. Platforms & environments\n5. Tech constraints\n6. Data & integrations\n7. Auth & permissions\n8. Performance & reliability\n9. Testing & validation\n10. Ask any helpful question\n\n### Phase 2: Retrieve Documentation\n\nWhen the plan involves any external library, API, framework, or service, use the Context7 skill to fetch the latest official docs before drafting tasks. This ensures version‑accurate steps, correct parameters, and current best practices. If no external dependencies apply, skip this phase.\n\n### Phase 3: Create Plan\n\n#### Structure\n- **Overview**: Brief summary and approach\n- **Sprints**: Logical phases that build on each other\n- **Tasks**: Specific, actionable items within sprints\n\n#### Sprint Requirements\nEach sprint must:\n- Result in **demoable, runnable, testable** increment\n- Build on prior sprint work\n- Include demo\u002Fverification checklist\n\n#### Task Requirements\nEach task must be:\n- **Atomic and committable** (small, independent)\n- Specific with clear inputs\u002Foutputs\n- Independently testable\n- Include file paths when relevant\n- Include dependencies for parallel execution\n- Include tests or validation method\n\n**Bad:** \"Implement Google OAuth\"\n**Good:**\n- \"Add Google OAuth config to env variables\"\n- \"Install passport-google-oauth20 package\"\n- \"Create OAuth callback route in src\u002Froutes\u002Fauth.ts\"\n- \"Add Google sign-in button to login UI\"\n\n### Phase 3: Save\nSave the file\n\nGenerate filename from request:\n1. Extract keywords\n2. Convert to kebab-case\n3. Add `-plan.md` suffix\n\nExamples:\n- \"fix xyz bug\" → `xyz-bug-plan.md`\n\n### Phase 4: Gotchas\n\nAFTER it is saved. Identify potential issues & edge cases in plan. Address proactively. Where could smth go wrong? What about the plan is ambiguous? Missing step, dependency, or pitfall?\n\nIf any gotchas found, stop & ask up to 3 more questions. (either w\u002F request_user_input or directly)\n\nRefine the plan if any additional useful info is provided.\n\n## Plan Template\n\n```markdown\n# Plan: [Task Name]\n\n**Generated**: [Date]\n**Estimated Complexity**: [Low\u002FMedium\u002FHigh]\n\n## Overview\n[Summary of task and approach]\n\n## Prerequisites\n- [Dependencies or requirements]\n- [Tools, libraries, access needed]\n\n## Sprint 1: [Name]\n**Goal**: [What this accomplishes]\n**Demo\u002FValidation**:\n- [How to run\u002Fdemo]\n- [What to verify]\n\n### Task 1.1: [Name]\n- **Location**: [File paths]\n- **Description**: [What to do]\n- **Dependencies**: [Previous tasks]\n- **Acceptance Criteria**:\n  - [Specific criteria]\n- **Validation**:\n  - [Tests or verification]\n\n### Task 1.2: [Name]\n[...]\n\n## Sprint 2: [Name]\n[...]\n\n## Testing Strategy\n- [How to test]\n- [What to verify per sprint]\n\n## Potential Risks & Gotchas\n- [What could go wrong]\n- [Mitigation strategies]\n\n## Rollback Plan\n- [How to undo if needed]\n```\n\n## Important\n\n- Think about full lifecycle: implementation, testing, deployment\n- Consider non-functional requirements\n- Show user summary and file path when done\n- Do NOT implement - only create the plan\n",{"name":5,"description":7},"main","6c13f6f4ac5a3bc1e6b78cd2bb1704f122c4a73e","archive\u002Fupstream\u002Fexamples\u002Fskills\u002Fplanner",0,"https:\u002F\u002Fgithub.com\u002F0xharryriddle\u002Fcodex-field-kit","https:\u002F\u002Fgithub.com\u002F0xharryriddle","https:\u002F\u002Fharryriddle.vercel.app","2026-04-11 11:49:51",{"source":8,"skillName":5,"commands":52,"prompt":62,"zipAvailable":63},[53,56,59],{"tool":54,"command":55},"npx","npx skills add 0xharryriddle\u002Fcodex-field-kit --skill planner",{"tool":57,"command":58},"bunx","bunx skills add 0xharryriddle\u002Fcodex-field-kit --skill planner",{"tool":60,"command":61},"pnpm","pnpm dlx skills add 0xharryriddle\u002Fcodex-field-kit --skill planner","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002F0xharryriddle\u002Fcodex-field-kit\u002Fblob\u002Fmain\u002Farchive\u002Fupstream\u002Fexamples\u002Fskills\u002Fplanner\u002FSKILL.md",true,[],[66,96,112,121,146,173],{"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":77,"publishedAt":38},"01M6H7ZKE6MR33HC84QZ1TA6MV","vercel-react-best-practices","React and Next.js performance optimization guidelines from Vercel Engineering. This skill should be used when writing, reviewing, or refactoring React\u002FNext.js code to ensure optimal performance patterns. Triggers on tasks involving React components, Next.js pages, data fetching, bundle optimization, or performance improvements.","https:\u002F\u002Fgithub.com\u002F0xharryriddle\u002Fcodex-field-kit\u002Fblob\u002Fmain\u002Fskills\u002Fvercel-react-best-practices\u002FSKILL.md",[72],{"categoryNo":73,"categoryName":74,"taxonomyType":75,"taxonomyTypeDesc":76},"01JBSEEDCAT000000000000009","前端开发","SCENARIO","使用场景",[78,79,80,81,82,37,83,24,84,85,86,87,88,89,90,91,92,93,94,95],"react best practices","react","vercel react best practices","best practices","vercel","data fetching","pages","next","performance optimization","refactoring","Next.js","Optimization","code","guidelines","react components","components","performance","writing",{"skillNo":97,"name":98,"nameZh":6,"description":99,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":100,"categories":101,"keywords":102,"publishedAt":38},"01M6H7ZGC2WK8SEKYHWDNTMDA9","swarm-planner","[EXPLICIT INVOCATION ONLY] Creates dependency-aware implementation plans optimized for parallel multi-agent execution.","https:\u002F\u002Fgithub.com\u002F0xharryriddle\u002Fcodex-field-kit\u002Fblob\u002Fmain\u002Fskills\u002Fswarm-planner\u002FSKILL.md",[],[103,104,5,105,106,107,108,25,109,20,110,111],"swarm","swarm planner","parallel","multi-agent","only","execution","dependency","multi","implementation",{"skillNo":113,"name":114,"nameZh":6,"description":115,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":116,"categories":117,"keywords":118,"publishedAt":38},"01M6H7ZD93853RZCYQWH1D38TM","super-swarm-spark","Only to be triggered by explicit super-swarm-spark commands.","https:\u002F\u002Fgithub.com\u002F0xharryriddle\u002Fcodex-field-kit\u002Fblob\u002Fmain\u002Fskills\u002Fsuper-swarm-spark\u002FSKILL.md",[],[119,103,120,107,26],"super swarm spark","spark",{"skillNo":122,"name":123,"nameZh":6,"description":124,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":125,"categories":126,"keywords":127,"publishedAt":38},"01M6H7Z987QBY49JCCPT953EAZ","role-creator","Create and install Codex custom agent roles in ~\u002F.codex\u002Fconfig.toml, generate role config files, enforce supported keys, and guide users through required role inputs (model, reasoning effort, developer_instructions).","https:\u002F\u002Fgithub.com\u002F0xharryriddle\u002Fcodex-field-kit\u002Fblob\u002Fmain\u002Fskills\u002Frole-creator\u002FSKILL.md",[],[128,129,130,131,132,133,134,135,136,137,138,139,140,141,142,36,143,144,145],"role","creator","role creator","keys","users","roles","toml","enforce","install","guide","instructions","model","developer","reasoning","generate","config","codex","files",{"skillNo":147,"name":148,"nameZh":6,"description":149,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":150,"categories":151,"keywords":155,"publishedAt":38},"01M6H7Z5TRPMDQ7YSZQXPN1G60","read-github","Read and search GitHub repository documentation via gitmcp.io MCP service.\n\n**WHEN TO USE:**\n- User provides a GitHub URL\n- User mentions a specific repo in owner\u002Frepo format\n- User asks \"what does this repo do?\", \"read the docs for X repo\", or similar\n- User wants to search code or docs within a repo","https:\u002F\u002Fgithub.com\u002F0xharryriddle\u002Fcodex-field-kit\u002Fblob\u002Fmain\u002Fskills\u002Fread-github\u002FSKILL.md",[152],{"categoryNo":153,"categoryName":154,"taxonomyType":75,"taxonomyTypeDesc":76},"01JBSEEDCAT000000000000023","Skill与智能体开发",[156,157,158,90,159,160,161,162,20,163,164,165,166,167,168,30,169,170,171,172],"github","read github","read","documentation","docs","MCP","search","when to use","URL","via","io","service","do","user","repo","format","repository",{"skillNo":174,"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":175,"categories":176,"keywords":177,"publishedAt":38},"01M6H7Z215CTKYJ4Y1X6EQWN6M","https:\u002F\u002Fgithub.com\u002F0xharryriddle\u002Fcodex-field-kit\u002Fblob\u002Fmain\u002Fskills\u002Fplanner\u002FSKILL.md",[],[5,27,20,21,22,23,24,25,26,28,19,30,31,32,33,34,35,36,37,29]]