[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7AVFXEVXB91MYH37JE52VR0":3,"skill-same:01M7AVFXEVXB91MYH37JE52VR0":54},{"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},"01M7AVFXEVXB91MYH37JE52VR0","planning-and-task-breakdown",null,"Use when shaping a rough idea, specifying an ambiguous feature, stress-testing a plan against code and project decisions, or turning an approved design into executable vertical slices.","MinhDuyDEV\u002Fmd-pikit","MinhDuyDEV","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F94704296?v=4","01M7AVDRJB5JM5VG5B6K49X0EZ","Nguyễn Viết Minh Duy","01M7AVDRKDB3JPGHFE4HGK1Z5M",0,"MIT","https:\u002F\u002Fgithub.com\u002FMinhDuyDEV\u002Fmd-pikit\u002Fblob\u002Fmain\u002F.pi\u002Fskills\u002Fplanning-and-task-breakdown\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: planning-and-task-breakdown\ndescription: Use when shaping a rough idea, specifying an ambiguous feature, stress-testing a plan against code and project decisions, or turning an approved design into executable vertical slices.\n---\n\n# Planning and Task Breakdown\n\n\u003CHARD-GATE>\nFor rough, ambiguous, or design-heavy work, do not write code or an implementation plan until the design is approved. If requirements and cause are already concrete and reversible, skip discovery and use incremental implementation.\n\u003C\u002FHARD-GATE>\n\n## 1. Discover the Design\n\nClassify unknowns before proposing:\n\n- **Known knowns:** stated facts.\n- **Known unknowns:** ask the user.\n- **Unknown knowns:** show 2–4 cheap variants or point at a reference.\n- **Unknown unknowns:** surface decision criteria and highest-risk blindspots.\n\nFor live alternatives, show trade-offs and recommend one. Ask one question at a time about the load-bearing architecture, data, UX, security, cost, or scope decision. State safe assumptions and their later verification. Use YAGNI against speculative scope, never against an explicit requirement.\n\n## 2. Write the Contract\n\n**Spec before code. The spec is the contract.** Minimum spec:\n\n```md\n## Goal\n\u003Cobservable outcome>\n## Non-goals\n\u003Cexplicit exclusions>\n## Acceptance criteria\n- [ ] \u003Ccheckable behavior>\n## Open questions\n- \u003Cmust resolve before implementation>\n```\n\nTests derive from acceptance criteria. Spec changes are explicit scope changes, recorded before implementation continues. Keep WHAT separate from the implementation plan's HOW.\n\n## 3. Stress-Test Material Decisions\n\nInspect code, tests, `CONTEXT.md` \u002F `CONTEXT-MAP.md`, and project ADRs under `docs\u002Fadr\u002F` first. If exploration can answer a question, explore instead of asking. Cross-check claims against code and call out conflicting glossary terms or vague or overloaded language.\n\nA blocking question must be:\n\n- **Material:** answer changes architecture, scope, UX, data, security, cost, or criteria.\n- **Grounded:** cite the concrete uncertainty.\n- **Answerable:** provide live options, a recommended answer, and default if the user does not care.\n\nProbe 10x scale, cost of being wrong, failure modes, rollback, uncontrolled dependencies, forgotten non-goals, and simplest validation. Stop when answers are concrete or questions repeat; do not grill reversible trivia or attack the user.\n\nCreate glossary files lazily; keep `CONTEXT.md` domain-only, not an implementation spec. See `references\u002FCONTEXT-FORMAT.md`. Offer a project ADR under `docs\u002Fadr\u002F` only when the decision is hard to reverse, surprising without context, and the result of a real trade-off; see `references\u002FADR-FORMAT.md`. Work-session decisions belong in `\u003Crepo-root>\u002F.pi\u002Fartifacts\u002FDECISIONS.md` under `development-lifecycle`.\n\n## 4. Build the Executable Plan\n\nOrder independently verifiable vertical slices:\n\n1. Put the **most-likely-to-change** model\u002Finterface\u002FUX or unknown integration first.\n2. Give each slice one observable outcome, verification command, risk, and clean rollback.\n3. Put mechanical rename\u002Freformat\u002Frefactor work last.\n4. Name open questions that block a slice and stop conditions for parallel workers.\n\n```md\n## Goal \u002F Non-goals\n## Slices\n1. \u003Cvertical outcome> — verify: \u003Ccommand> — risk: \u003Cfailure>\n## Open questions\n## Stop conditions\n```\n\nReject plans that begin with horizontal setup, accept “looks right,” omit non-goals, or cannot verify slices independently.\n","# Planning and Task Breakdown\n\n\u003CHARD-GATE>\nFor rough, ambiguous, or design-heavy work, do not write code or an implementation plan until the design is approved. If requirements and cause are already concrete and reversible, skip discovery and use incremental implementation.\n\u003C\u002FHARD-GATE>\n\n## 1. Discover the Design\n\nClassify unknowns before proposing:\n\n- **Known knowns:** stated facts.\n- **Known unknowns:** ask the user.\n- **Unknown knowns:** show 2–4 cheap variants or point at a reference.\n- **Unknown unknowns:** surface decision criteria and highest-risk blindspots.\n\nFor live alternatives, show trade-offs and recommend one. Ask one question at a time about the load-bearing architecture, data, UX, security, cost, or scope decision. State safe assumptions and their later verification. Use YAGNI against speculative scope, never against an explicit requirement.\n\n## 2. Write the Contract\n\n**Spec before code. The spec is the contract.** Minimum spec:\n\n```md\n## Goal\n\u003Cobservable outcome>\n## Non-goals\n\u003Cexplicit exclusions>\n## Acceptance criteria\n- [ ] \u003Ccheckable behavior>\n## Open questions\n- \u003Cmust resolve before implementation>\n```\n\nTests derive from acceptance criteria. Spec changes are explicit scope changes, recorded before implementation continues. Keep WHAT separate from the implementation plan's HOW.\n\n## 3. Stress-Test Material Decisions\n\nInspect code, tests, `CONTEXT.md` \u002F `CONTEXT-MAP.md`, and project ADRs under `docs\u002Fadr\u002F` first. If exploration can answer a question, explore instead of asking. Cross-check claims against code and call out conflicting glossary terms or vague or overloaded language.\n\nA blocking question must be:\n\n- **Material:** answer changes architecture, scope, UX, data, security, cost, or criteria.\n- **Grounded:** cite the concrete uncertainty.\n- **Answerable:** provide live options, a recommended answer, and default if the user does not care.\n\nProbe 10x scale, cost of being wrong, failure modes, rollback, uncontrolled dependencies, forgotten non-goals, and simplest validation. Stop when answers are concrete or questions repeat; do not grill reversible trivia or attack the user.\n\nCreate glossary files lazily; keep `CONTEXT.md` domain-only, not an implementation spec. See `references\u002FCONTEXT-FORMAT.md`. Offer a project ADR under `docs\u002Fadr\u002F` only when the decision is hard to reverse, surprising without context, and the result of a real trade-off; see `references\u002FADR-FORMAT.md`. Work-session decisions belong in `\u003Crepo-root>\u002F.pi\u002Fartifacts\u002FDECISIONS.md` under `development-lifecycle`.\n\n## 4. Build the Executable Plan\n\nOrder independently verifiable vertical slices:\n\n1. Put the **most-likely-to-change** model\u002Finterface\u002FUX or unknown integration first.\n2. Give each slice one observable outcome, verification command, risk, and clean rollback.\n3. Put mechanical rename\u002Freformat\u002Frefactor work last.\n4. Name open questions that block a slice and stop conditions for parallel workers.\n\n```md\n## Goal \u002F Non-goals\n## Slices\n1. \u003Cvertical outcome> — verify: \u003Ccommand> — risk: \u003Cfailure>\n## Open questions\n## Stop conditions\n```\n\nReject plans that begin with horizontal setup, accept “looks right,” omit non-goals, or cannot verify slices independently.\n",{"name":5,"description":7},"main","01207a96514af9f9c4d7d6cb594b936c6a9ddb10",".pi\u002Fskills\u002Fplanning-and-task-breakdown","https:\u002F\u002Fgithub.com\u002FMinhDuyDEV\u002Fmd-pikit","https:\u002F\u002Fgithub.com\u002FMinhDuyDEV","2026-08-20 02:00:33",{"source":8,"skillName":5,"commands":31,"prompt":41,"zipAvailable":42},[32,35,38],{"tool":33,"command":34},"npx","npx skills add MinhDuyDEV\u002Fmd-pikit --skill planning-and-task-breakdown",{"tool":36,"command":37},"bunx","bunx skills add MinhDuyDEV\u002Fmd-pikit --skill planning-and-task-breakdown",{"tool":39,"command":40},"pnpm","pnpm dlx skills add MinhDuyDEV\u002Fmd-pikit --skill planning-and-task-breakdown","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FMinhDuyDEV\u002Fmd-pikit\u002Fblob\u002Fmain\u002F.pi\u002Fskills\u002Fplanning-and-task-breakdown\u002FSKILL.md",true,[44,50],{"path":45,"resourceType":46,"resourceTypeDesc":47,"sizeBytes":48,"sourceHtmlUrl":49},"references\u002FADR-FORMAT.md","REFERENCE","参考文档",2766,"https:\u002F\u002Fgithub.com\u002FMinhDuyDEV\u002Fmd-pikit\u002Fblob\u002Fmain\u002F.pi\u002Fskills\u002Fplanning-and-task-breakdown\u002Freferences\u002FADR-FORMAT.md",{"path":51,"resourceType":46,"resourceTypeDesc":47,"sizeBytes":52,"sourceHtmlUrl":53},"references\u002FCONTEXT-FORMAT.md",2299,"https:\u002F\u002Fgithub.com\u002FMinhDuyDEV\u002Fmd-pikit\u002Fblob\u002Fmain\u002F.pi\u002Fskills\u002Fplanning-and-task-breakdown\u002Freferences\u002FCONTEXT-FORMAT.md",[55,62,69,76,83,90],{"skillNo":56,"name":57,"nameZh":6,"description":58,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":59,"categories":60,"keywords":61,"publishedAt":19},"01M7AVGJR1RSRVA3VJT8ZW4Y27","writing-skills","Use when creating new skills, editing existing skills, or verifying skills work before deployment - applies TDD to process documentation by testing with subagents before writing, iterating until bulletproof against rationalization. Includes complete pressure testing methodology.","https:\u002F\u002Fgithub.com\u002FMinhDuyDEV\u002Fmd-pikit\u002Fblob\u002Fmain\u002F.pi\u002Fskills\u002Fwriting-skills\u002FSKILL.md",[],[],{"skillNo":63,"name":64,"nameZh":6,"description":65,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":66,"categories":67,"keywords":68,"publishedAt":19},"01M7AVGE076BNB3J7JDBGAKD2T","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\u002FMinhDuyDEV\u002Fmd-pikit\u002Fblob\u002Fmain\u002F.pi\u002Fskills\u002Fverification-before-completion\u002FSKILL.md",[],[],{"skillNo":70,"name":71,"nameZh":6,"description":72,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":73,"categories":74,"keywords":75,"publishedAt":19},"01M7AVGAYJ6APXRB9QWBG7482S","typescript-coding-standards","Use when writing, refactoring, or reviewing TypeScript code that needs strong domain modeling, typed errors, schema parsing, safe adapters, test seams, or maintainable module boundaries.","https:\u002F\u002Fgithub.com\u002FMinhDuyDEV\u002Fmd-pikit\u002Fblob\u002Fmain\u002F.pi\u002Fskills\u002Ftypescript-coding-standards\u002FSKILL.md",[],[],{"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":19},"01M7AVG8CE5BTR2CRFPHHVJCJZ","test-driven-development","Use when implementing a feature, bugfix, or behavior-changing refactor — require a failing behavior test before production code, then make the smallest change that passes.","https:\u002F\u002Fgithub.com\u002FMinhDuyDEV\u002Fmd-pikit\u002Fblob\u002Fmain\u002F.pi\u002Fskills\u002Ftest-driven-development\u002FSKILL.md",[],[],{"skillNo":84,"name":85,"nameZh":6,"description":86,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":87,"categories":88,"keywords":89,"publishedAt":19},"01M7AVG5FJH3WTG9XR2G0608ND","source-driven-development","Use when unfamiliar libraries, dependency internals, external APIs, framework behavior, migrations, or current ecosystem guidance require official documentation, version-matched source, read the tests, and cited evidence.","https:\u002F\u002Fgithub.com\u002FMinhDuyDEV\u002Fmd-pikit\u002Fblob\u002Fmain\u002F.pi\u002Fskills\u002Fsource-driven-development\u002FSKILL.md",[],[],{"skillNo":91,"name":92,"nameZh":6,"description":93,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":94,"categories":95,"keywords":96,"publishedAt":19},"01M7AVG37PZ77CF35KAR6E93ZJ","security-and-hardening","Use when auditing security, implementing authentication or authorization, handling secrets, or validating data across external trust boundaries.","https:\u002F\u002Fgithub.com\u002FMinhDuyDEV\u002Fmd-pikit\u002Fblob\u002Fmain\u002F.pi\u002Fskills\u002Fsecurity-and-hardening\u002FSKILL.md",[],[]]