[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6MHWFYG8646N651B4AB26BT":3,"skill-same:01M6MHWFYG8646N651B4AB26BT":66},{"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":23,"publishedAt":37,"linkOnly":38,"markdownContent":39,"markdownBody":40,"frontMatter":41,"refName":42,"commitSha":43,"skillDirectory":44,"forksCount":45,"repositoryHtmlUrl":46,"repositoryHomepageUrl":47,"ownerHtmlUrl":48,"ownerBlogUrl":49,"ownerDescription":50,"updatedAt":51,"install":52,"resources":65},"01M6MHWFYG8646N651B4AB26BT","implementation-planner",null,"Use after requirements, contracts, and visual gates pass to create a TDD-ready implementation plan.","hashgraph-online\u002Fawesome-codex-plugins","hashgraph-online","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F160371962?v=4","01M6CNB6NRJVNNGN14TR01Q6D3","HOL (Hashgraph Online)","01M6JT1HSKKG9V68KQAQGBA7XP",1575,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fkevin592\u002Fcodex-full-stack-workflow\u002Fskills\u002Fimplementation-planner\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[24,25,26,27,28,29,30,31,32,33,34,35,36],"planner","implementation","implementation planner","tdd","create","plan","use","ready","contracts","visual","requirements","gates","implementation plan","2026-11-10 10:12:30",false,"---\nname: implementation-planner\ndescription: Use after requirements, contracts, and visual gates pass to create a TDD-ready implementation plan.\n---\n\n# Implementation Planner\n\nThis skill creates a task-by-task implementation plan that can be executed with TDD and reviewed after each task.\n\nIt is also the bridge from full-stack product contracts into Superpowers execution discipline. Every implementation plan must declare its lifecycle intensity and include a concrete handoff to the execution skills that will carry the work.\n\n## Input Artifacts\n\n- `00-stage.json`\n- `00-artifact-registry.json`\n- Product, IA, interaction, state, backend\u002FAPI\u002Ffrontend, visual, and acceptance contracts\n- Visual confirmation when UI applies\n\n## Output Artifact\n\n- `docs\u002Ffull-stack-development\u002Frequirements\u002F\u003Cfeature-slug>\u002F05-implementation\u002Fimplementation-plan.md`\n\n## Required MCP Tool\n\n- `review_stage_gate`\n- `review_artifact_contract`\n- `review_visual_evidence` when UI applies\n- `generate_frontend_verification_checklist` when UI applies\n- `select_development_flow_profile`\n- `plan_superpowers_execution_handoff`\n\n## Hard Stops\n\n- Do not plan implementation when requirements are unapproved.\n- Do not plan UI implementation when Pencil\u002FFigma evidence is missing, incomplete, stale, or not reviewed.\n- Do not create tasks without test commands and expected failure reasons.\n- Do not create an implementation plan without one flow profile: `strict-fullstack`, `strict-ui`, `light-change`, or `debug-fix`.\n- Do not begin implementation until `plan_superpowers_execution_handoff` has attached TDD, subagent-driven or executing-plans, requesting-code-review, verification-before-completion, and finishing-a-development-branch.\n- Do not let `light-change` bypass change records or completion evidence when requirements or code changed.\n- Do not let `debug-fix` skip root-cause evidence or a failing regression test before the fix.\n\n## Pressure Test Responsibility\n\n- Plans without failing tests block.\n- Plans without exact files block.\n- Plans without verification commands block.\n- Plans without a flow profile block.\n- Plans without Superpowers execution handoff block.\n\n## Flow Profiles\n\n| Profile | Use When | Required Emphasis |\n| --- | --- | --- |\n| `strict-fullstack` | Product, UI, backend, API, data, auth, or acceptance contracts may change. | Full requirements workspace, visual evidence when UI applies, backend\u002FAPI audit, code review, completion gate. |\n| `strict-ui` | React Web UI, HeroUI, visual design, responsive state, or interaction behavior changes without backend\u002FAPI changes. | HeroUI official docs, Pencil\u002FFigma evidence, visual inspection metrics, component graph audit. |\n| `light-change` | Small docs, copy, config, or narrowly bounded code changes that do not alter product scope, IA, UI, backend, API, data, auth, or acceptance behavior. | Change record when requirements changed, targeted verification, completion gate. |\n| `debug-fix` | Bug, failed test, broken build, regression, or unexpected behavior. | Root-cause investigation, failing regression test, targeted fix, fresh verification. |\n\n## Superpowers Execution Handoff\n\nAfter the implementation plan passes this skill, attach this handoff:\n\n- `superpowers:test-driven-development`: production code requires a previously observed failing test.\n- `superpowers:subagent-driven-development`: default for independent tasks; use one fresh implementer and one reviewer per task.\n- `superpowers:executing-plans`: fallback only when subagents are unavailable or tasks are tightly coupled.\n- `superpowers:requesting-code-review`: required after each substantial task and before final completion.\n- `superpowers:verification-before-completion`: fresh evidence before any completion claim.\n- `superpowers:finishing-a-development-branch`: structured branch finish after tests pass.\n\nRequired execution artifacts: task brief, task report, review package, `.superpowers\u002Fsdd\u002Fprogress.md`, final code review report, and final acceptance report.\n\n## Next Gate\n\n- `implementation-in-progress` may start only after the implementation plan artifact passes review, a flow profile is selected, and the Superpowers execution handoff is attached.\n","# Implementation Planner\n\nThis skill creates a task-by-task implementation plan that can be executed with TDD and reviewed after each task.\n\nIt is also the bridge from full-stack product contracts into Superpowers execution discipline. Every implementation plan must declare its lifecycle intensity and include a concrete handoff to the execution skills that will carry the work.\n\n## Input Artifacts\n\n- `00-stage.json`\n- `00-artifact-registry.json`\n- Product, IA, interaction, state, backend\u002FAPI\u002Ffrontend, visual, and acceptance contracts\n- Visual confirmation when UI applies\n\n## Output Artifact\n\n- `docs\u002Ffull-stack-development\u002Frequirements\u002F\u003Cfeature-slug>\u002F05-implementation\u002Fimplementation-plan.md`\n\n## Required MCP Tool\n\n- `review_stage_gate`\n- `review_artifact_contract`\n- `review_visual_evidence` when UI applies\n- `generate_frontend_verification_checklist` when UI applies\n- `select_development_flow_profile`\n- `plan_superpowers_execution_handoff`\n\n## Hard Stops\n\n- Do not plan implementation when requirements are unapproved.\n- Do not plan UI implementation when Pencil\u002FFigma evidence is missing, incomplete, stale, or not reviewed.\n- Do not create tasks without test commands and expected failure reasons.\n- Do not create an implementation plan without one flow profile: `strict-fullstack`, `strict-ui`, `light-change`, or `debug-fix`.\n- Do not begin implementation until `plan_superpowers_execution_handoff` has attached TDD, subagent-driven or executing-plans, requesting-code-review, verification-before-completion, and finishing-a-development-branch.\n- Do not let `light-change` bypass change records or completion evidence when requirements or code changed.\n- Do not let `debug-fix` skip root-cause evidence or a failing regression test before the fix.\n\n## Pressure Test Responsibility\n\n- Plans without failing tests block.\n- Plans without exact files block.\n- Plans without verification commands block.\n- Plans without a flow profile block.\n- Plans without Superpowers execution handoff block.\n\n## Flow Profiles\n\n| Profile | Use When | Required Emphasis |\n| --- | --- | --- |\n| `strict-fullstack` | Product, UI, backend, API, data, auth, or acceptance contracts may change. | Full requirements workspace, visual evidence when UI applies, backend\u002FAPI audit, code review, completion gate. |\n| `strict-ui` | React Web UI, HeroUI, visual design, responsive state, or interaction behavior changes without backend\u002FAPI changes. | HeroUI official docs, Pencil\u002FFigma evidence, visual inspection metrics, component graph audit. |\n| `light-change` | Small docs, copy, config, or narrowly bounded code changes that do not alter product scope, IA, UI, backend, API, data, auth, or acceptance behavior. | Change record when requirements changed, targeted verification, completion gate. |\n| `debug-fix` | Bug, failed test, broken build, regression, or unexpected behavior. | Root-cause investigation, failing regression test, targeted fix, fresh verification. |\n\n## Superpowers Execution Handoff\n\nAfter the implementation plan passes this skill, attach this handoff:\n\n- `superpowers:test-driven-development`: production code requires a previously observed failing test.\n- `superpowers:subagent-driven-development`: default for independent tasks; use one fresh implementer and one reviewer per task.\n- `superpowers:executing-plans`: fallback only when subagents are unavailable or tasks are tightly coupled.\n- `superpowers:requesting-code-review`: required after each substantial task and before final completion.\n- `superpowers:verification-before-completion`: fresh evidence before any completion claim.\n- `superpowers:finishing-a-development-branch`: structured branch finish after tests pass.\n\nRequired execution artifacts: task brief, task report, review package, `.superpowers\u002Fsdd\u002Fprogress.md`, final code review report, and final acceptance report.\n\n## Next Gate\n\n- `implementation-in-progress` may start only after the implementation plan artifact passes review, a flow profile is selected, and the Superpowers execution handoff is attached.\n",{"name":5,"description":7},"main","2b63f856ce19c2a797929cacabd9e0fc936812fa","plugins\u002Fkevin592\u002Fcodex-full-stack-workflow\u002Fskills\u002Fimplementation-planner",491,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins","https:\u002F\u002Fhol.org\u002Fplugins\u002Fbest-codex-plugins","https:\u002F\u002Fgithub.com\u002Fhashgraph-online","https:\u002F\u002Fhol.org","Open-source standards and developer tools for interoperable AI agents: discovery, identity, communication, payments, privacy and security.","2026-11-14 14:06:13",{"source":8,"skillName":5,"commands":53,"prompt":63,"zipAvailable":64},[54,57,60],{"tool":55,"command":56},"npx","npx skills add hashgraph-online\u002Fawesome-codex-plugins --skill implementation-planner",{"tool":58,"command":59},"bunx","bunx skills add hashgraph-online\u002Fawesome-codex-plugins --skill implementation-planner",{"tool":61,"command":62},"pnpm","pnpm dlx skills add hashgraph-online\u002Fawesome-codex-plugins --skill implementation-planner","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fkevin592\u002Fcodex-full-stack-workflow\u002Fskills\u002Fimplementation-planner\u002FSKILL.md",true,[],[67,77,85,93,101,109],{"skillNo":68,"name":69,"nameZh":6,"description":70,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":71,"licenseFileUrl":72,"sourceHtmlUrl":73,"categories":74,"keywords":75,"publishedAt":76},"01M7DV332YQMGD8WTRJ9DZQXTB","worktable-review-with-annotations","Create, inspect, reply to, update, or resolve situated Worktable annotations. Use when feedback belongs to a Doc section, block, text range, or HTML Doc, or when the user asks to address existing review feedback and coordinate a requested artifact edit.","MIT","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-review-with-annotations\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-review-with-annotations\u002FSKILL.md",[],[],"2026-11-15 14:19:17",{"skillNo":78,"name":79,"nameZh":6,"description":80,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":71,"licenseFileUrl":81,"sourceHtmlUrl":82,"categories":83,"keywords":84,"publishedAt":76},"01M7DV2YGHCZVBEB1AHYB6CGHE","worktable-find-and-synthesize-context","Find, assess, and synthesize context from Worktable Docs and Records. Use when the user asks what a workspace contains, wants workspace-backed research, needs current facts reconciled across artifacts, or requests a cited synthesis without changing workspace state.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-find-and-synthesize-context\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-find-and-synthesize-context\u002FSKILL.md",[],[],{"skillNo":86,"name":87,"nameZh":6,"description":88,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":71,"licenseFileUrl":89,"sourceHtmlUrl":90,"categories":91,"keywords":92,"publishedAt":76},"01M7DV2TQN1H11ME2SAF9MXN7V","worktable-create-or-update-docs","Create, edit, rename, or maintain narrative Worktable Docs. Use for plans, decisions, briefs, notes, research syntheses, and other durable prose when the user requests a new artifact or a safe update to an existing one.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-update-docs\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-update-docs\u002FSKILL.md",[],[],{"skillNo":94,"name":95,"nameZh":6,"description":96,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":71,"licenseFileUrl":97,"sourceHtmlUrl":98,"categories":99,"keywords":100,"publishedAt":76},"01M7DV2NE452NEA8TXATKSNAJH","worktable-create-or-manage-records","Organize repeated structured information as durable Worktable Records. Use for research datasets, inventories, directories, pipelines, trackers, and other collections whose items need identity, fields, filtering, links, validation, or individual updates.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-manage-records\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-manage-records\u002FSKILL.md",[],[],{"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":71,"licenseFileUrl":105,"sourceHtmlUrl":106,"categories":107,"keywords":108,"publishedAt":76},"01M7DV2HENRBR2KSCVM064WH0Y","worktable-create-or-manage-interactive-html","Create or improve durable visual and interactive artifacts in Worktable. Use for dashboards, trackers, calculators, mini apps, slide presentations, and other requests that benefit from a polished HTML Doc.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-manage-interactive-html\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-manage-interactive-html\u002FSKILL.md",[],[],{"skillNo":110,"name":111,"nameZh":6,"description":112,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":71,"licenseFileUrl":113,"sourceHtmlUrl":114,"categories":115,"keywords":116,"publishedAt":76},"01M7DV2CADR5R7RQFFYPNAGR9Y","worktable-collaborate-threads","Read, answer, and hand off messages through durable Worktable threads with users or other authenticated participants. Use when the user asks to check addressed messages, reply to a participant, continue a thread, request another agent's help, wait briefly for a response, or watch for comments and messages sent to the agent.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-collaborate-threads\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-collaborate-threads\u002FSKILL.md",[],[]]