[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6GGE3P1SS5MPQN7XMHC2D39":3,"skill-same:01M6GGE3P1SS5MPQN7XMHC2D39":55},{"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":29,"linkOnly":30,"markdownContent":31,"markdownBody":32,"frontMatter":33,"refName":34,"commitSha":35,"skillDirectory":36,"forksCount":37,"repositoryHtmlUrl":38,"repositoryHomepageUrl":6,"ownerHtmlUrl":39,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":40,"install":41,"resources":54},"01M6GGE3P1SS5MPQN7XMHC2D39","task-planner",null,"When decomposing a feature or spec into implementable subtasks, estimating scope, or orchestrating multi-step work across subagents.","ahmadulhoq\u002Fagentskel","ahmadulhoq","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F3884252?v=4","01M6GGC32SQTQ52FY4JB14FYSY","Ahmadul Hoq","01M6GGC37CJEYM63V3WEHY4Y8V",13,"MIT","https:\u002F\u002Fgithub.com\u002Fahmadulhoq\u002Fagentskel\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Ftask-planner\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28],"planner","task","task planner","spec","work","subagents","across","feature","scope","multi","2026-11-10 10:12:30",false,"---\nname: task-planner\nlicense: MIT\ndescription: When decomposing a feature or spec into implementable subtasks, estimating scope, or orchestrating multi-step work across subagents.\n---\n\n# Task Planner Standards\n\n## Task Management\n1. **Plan First:** Write plan with checkable items before starting.\n2. **Verify Plan:** Check in with the user before executing.\n3. **Track Progress:** Mark items complete as you go.\n4. **Explain Changes:** High-level summary at each step.\n5. **Document Results:** Add review section when complete.\n6. **Capture Lessons:** Update `.memory\u002FLESSONS.md` after corrections.\n\n## Task Quality\n- Tasks must be clear, specific, and actionable.\n- Complex tasks must be broken into atomic, trackable subtasks.\n- Dependencies between tasks must be explicitly declared.\n- Security-related tasks must undergo mandatory review.\n- Escalate ambiguous or contradictory tasks for clarification.\n\n## Blueprint Check (if configured)\n\nIf `Blueprint Path` is set in `.memory\u002FCONFIG.md` and the task involves shared\nbusiness logic:\n- [ ] Read the relevant spec(s) in `[BLUEPRINT_PATH]\u002Fspecs\u002F` before planning.\n- [ ] Check `[BLUEPRINT_PATH]\u002Fparity\u002FPARITY_MATRIX.md` for current platform status.\n- [ ] Include in the plan: \"Requires Knowledge Bus entry\" if the change affects\n      cross-platform contracts.\n- [ ] Note any spec gaps — if the spec is missing or incomplete, plan a spec\n      update as part of the task.\n\nSkip this section if no blueprint is configured or the task is project-specific.\n\n## Change Tracking\n- All rule or config changes must be documented in CHANGELOG.md.\n- Record source, timestamp, and rationale when modifying shared assets.\n- A rollback plan must be defined for every major change.\n\n## Subagent Strategy\n\nWhen a task benefits from fresh context, parallel execution, or isolated scope,\nuse the **`subagent-dispatch`** skill. It provides prompt templates for\nimplementer, reviewer, and researcher subagents with explicit scope boundaries\nand result validation.\n\n**When to dispatch:**\n- Subtasks are independent and can proceed in parallel\n- Parallel execution provides meaningful time savings\n- Fresh context helps (no accumulated conversation noise)\n- Scope of each subtask is clear and self-contained\n\n**When NOT to dispatch:**\n- Iterative feedback from the user is needed between steps\n- The task is simpler to do directly in the current session\n- Subtasks need full conversation history or shared state\n- Scope is unclear or likely to shift during execution\n","# Task Planner Standards\n\n## Task Management\n1. **Plan First:** Write plan with checkable items before starting.\n2. **Verify Plan:** Check in with the user before executing.\n3. **Track Progress:** Mark items complete as you go.\n4. **Explain Changes:** High-level summary at each step.\n5. **Document Results:** Add review section when complete.\n6. **Capture Lessons:** Update `.memory\u002FLESSONS.md` after corrections.\n\n## Task Quality\n- Tasks must be clear, specific, and actionable.\n- Complex tasks must be broken into atomic, trackable subtasks.\n- Dependencies between tasks must be explicitly declared.\n- Security-related tasks must undergo mandatory review.\n- Escalate ambiguous or contradictory tasks for clarification.\n\n## Blueprint Check (if configured)\n\nIf `Blueprint Path` is set in `.memory\u002FCONFIG.md` and the task involves shared\nbusiness logic:\n- [ ] Read the relevant spec(s) in `[BLUEPRINT_PATH]\u002Fspecs\u002F` before planning.\n- [ ] Check `[BLUEPRINT_PATH]\u002Fparity\u002FPARITY_MATRIX.md` for current platform status.\n- [ ] Include in the plan: \"Requires Knowledge Bus entry\" if the change affects\n      cross-platform contracts.\n- [ ] Note any spec gaps — if the spec is missing or incomplete, plan a spec\n      update as part of the task.\n\nSkip this section if no blueprint is configured or the task is project-specific.\n\n## Change Tracking\n- All rule or config changes must be documented in CHANGELOG.md.\n- Record source, timestamp, and rationale when modifying shared assets.\n- A rollback plan must be defined for every major change.\n\n## Subagent Strategy\n\nWhen a task benefits from fresh context, parallel execution, or isolated scope,\nuse the **`subagent-dispatch`** skill. It provides prompt templates for\nimplementer, reviewer, and researcher subagents with explicit scope boundaries\nand result validation.\n\n**When to dispatch:**\n- Subtasks are independent and can proceed in parallel\n- Parallel execution provides meaningful time savings\n- Fresh context helps (no accumulated conversation noise)\n- Scope of each subtask is clear and self-contained\n\n**When NOT to dispatch:**\n- Iterative feedback from the user is needed between steps\n- The task is simpler to do directly in the current session\n- Subtasks need full conversation history or shared state\n- Scope is unclear or likely to shift during execution\n",{"name":5,"license":15,"description":7},"main","d94c109a4fad51623dc6048315860e53b32673fb",".agents\u002Fskills\u002Ftask-planner",3,"https:\u002F\u002Fgithub.com\u002Fahmadulhoq\u002Fagentskel","https:\u002F\u002Fgithub.com\u002Fahmadulhoq","2026-11-07 00:53:22",{"source":8,"skillName":5,"commands":42,"prompt":52,"zipAvailable":53},[43,46,49],{"tool":44,"command":45},"npx","npx skills add ahmadulhoq\u002Fagentskel --skill task-planner",{"tool":47,"command":48},"bunx","bunx skills add ahmadulhoq\u002Fagentskel --skill task-planner",{"tool":50,"command":51},"pnpm","pnpm dlx skills add ahmadulhoq\u002Fagentskel --skill task-planner","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fahmadulhoq\u002Fagentskel\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Ftask-planner\u002FSKILL.md",true,[],[56,76,101,127,151,156],{"skillNo":57,"name":58,"nameZh":6,"description":59,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":60,"categories":61,"keywords":62,"publishedAt":29},"01M6GGSN2D57Y8BR50X08Y695H","setup-project","When setting up agentskel on a new project that does not yet have .memory\u002F or .agents\u002F. Use when the user says \"set up agentskel\", \"install agentskel\", or \"add agent memory to this project\".","https:\u002F\u002Fgithub.com\u002Fahmadulhoq\u002Fagentskel\u002Fblob\u002Fmain\u002Fskills\u002Fsetup-project\u002FSKILL.md",[],[63,64,65,66,67,68,69,70,71,72,73,74,75],"setup project","project","setup","memory","add","up","use","install","add agent","user","new project","SET","agent memory",{"skillNo":77,"name":78,"nameZh":6,"description":79,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":80,"categories":81,"keywords":82,"publishedAt":29},"01M6GGSJ6HD2DFVZQTESJ81GYM","using-git-worktrees","When running long feature implementations, parallel branch work, or build\u002Ftest scripts that must not interfere with the user's active working directory. Creates isolated execution environments via git worktrees in sibling directories.","https:\u002F\u002Fgithub.com\u002Fahmadulhoq\u002Fagentskel\u002Fblob\u002Fmain\u002Froles\u002Fdev\u002Fskills\u002Fusing-git-worktrees\u002FSKILL.md",[],[83,84,85,86,87,88,89,90,91,23,92,93,94,95,96,97,98,26,99,100],"git worktrees","worktrees","git","using git worktrees","Using git","test","directory","execution","parallel","branch","directories","environments","with","via","long","scripts","active","build",{"skillNo":102,"name":103,"nameZh":6,"description":104,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":105,"categories":106,"keywords":112,"publishedAt":29},"01M6GGSCFPK7MDSZH96XTNZR9B","test-engineer","When designing test strategy, analysing coverage, or writing tests outside the TDD cycle. Also use when working with CI pipelines or validating changes end-to-end.","https:\u002F\u002Fgithub.com\u002Fahmadulhoq\u002Fagentskel\u002Fblob\u002Fmain\u002Froles\u002Fdev\u002Fskills\u002Ftest-engineer\u002FSKILL.md",[107],{"categoryNo":108,"categoryName":109,"taxonomyType":110,"taxonomyTypeDesc":111},"01JBSEEDCAT000000000000008","测试与质量","SCENARIO","使用场景",[113,114,88,115,116,117,118,119,120,69,121,95,122,123,124,125,126],"test engineer","engineer","tests","tdd cycle","cycle","end","test strategy","pipelines","tdd","strategy","ci","writing tests","writing","coverage",{"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":137,"publishedAt":29},"01M6GGS8YA9XZB6DWV22JC0YTB","test-driven-development","When implementing logic changes during develop-feature or implement-task. Use the Red-Green-Refactor cycle to write a failing test before any production code.","https:\u002F\u002Fgithub.com\u002Fahmadulhoq\u002Fagentskel\u002Fblob\u002Fmain\u002Froles\u002Fdev\u002Fskills\u002Ftest-driven-development\u002FSKILL.md",[133,136],{"categoryNo":134,"categoryName":135,"taxonomyType":110,"taxonomyTypeDesc":111},"01JBSEEDCAT000000000000007","代码审查",{"categoryNo":108,"categoryName":109,"taxonomyType":110,"taxonomyTypeDesc":111},[138,139,88,140,20,141,26,142,143,117,144,69,145,146,147,148,149,150],"development","test driven development","driven","red","logic","green","red-green-refactor","write","develop","refactor","Production","code","implement",{"skillNo":152,"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":153,"categories":154,"keywords":155,"publishedAt":29},"01M6GGS61D41ZJG4D8XAS97H62","https:\u002F\u002Fgithub.com\u002Fahmadulhoq\u002Fagentskel\u002Fblob\u002Fmain\u002Froles\u002Fdev\u002Fskills\u002Ftask-planner\u002FSKILL.md",[],[21,20,19,26,25,24,23,22,27,28],{"skillNo":157,"name":158,"nameZh":6,"description":159,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":160,"categories":161,"keywords":162,"publishedAt":29},"01M6GGS30NJW4Q7QN4KVT0CV08","systematic-debugger","When applying debugging techniques during any investigation — root cause tracing, bisect, defense-in-depth. Enforces hypothesis-first analysis and prohibits guess-and-check changes. Use standalone or inside the debug-issue workflow.","https:\u002F\u002Fgithub.com\u002Fahmadulhoq\u002Fagentskel\u002Fblob\u002Fmain\u002Froles\u002Fdev\u002Fskills\u002Fsystematic-debugger\u002FSKILL.md",[],[163,164,165,166,167,168,169,170,69,171,172,173,174,175,176,177,178,179,180,181],"systematic debugger","systematic","debugger","check","standalone","root","issue workflow","issue","bisect","investigation","analysis","first","defense","hypothesis","defense-in-depth","tracing","debugging","debug","workflow"]