implementation-planner
Use after requirements, contracts, and visual gates pass to create a TDD-ready implementation plan.
- License 许可
- Apache-2.0
- 最近更新
- 2026-11-14
- Stars
- ★ 1.6k
- Forks
- 491
01 前言 Front Matter
- name
- implementation-planner
- description
- Use after requirements, contracts, and visual gates pass to create a TDD-ready implementation plan.
03 SKILL.md 正文
Implementation Planner
This skill creates a task-by-task implementation plan that can be executed with TDD and reviewed after each task.
It 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.
Input Artifacts
00-stage.json00-artifact-registry.json- Product, IA, interaction, state, backend/API/frontend, visual, and acceptance contracts
- Visual confirmation when UI applies
Output Artifact
docs/full-stack-development/requirements/<feature-slug>/05-implementation/implementation-plan.md
Required MCP Tool
review_stage_gatereview_artifact_contractreview_visual_evidencewhen UI appliesgenerate_frontend_verification_checklistwhen UI appliesselect_development_flow_profileplan_superpowers_execution_handoff
Hard Stops
- Do not plan implementation when requirements are unapproved.
- Do not plan UI implementation when Pencil/Figma evidence is missing, incomplete, stale, or not reviewed.
- Do not create tasks without test commands and expected failure reasons.
- Do not create an implementation plan without one flow profile:
strict-fullstack,strict-ui,light-change, ordebug-fix. - Do not begin implementation until
plan_superpowers_execution_handoffhas attached TDD, subagent-driven or executing-plans, requesting-code-review, verification-before-completion, and finishing-a-development-branch. - Do not let
light-changebypass change records or completion evidence when requirements or code changed. - Do not let
debug-fixskip root-cause evidence or a failing regression test before the fix.
Pressure Test Responsibility
- Plans without failing tests block.
- Plans without exact files block.
- Plans without verification commands block.
- Plans without a flow profile block.
- Plans without Superpowers execution handoff block.
Flow Profiles
| Profile | Use When | Required Emphasis |
|---|---|---|
strict-fullstack |
Product, UI, backend, API, data, auth, or acceptance contracts may change. | Full requirements workspace, visual evidence when UI applies, backend/API audit, code review, completion gate. |
strict-ui |
React Web UI, HeroUI, visual design, responsive state, or interaction behavior changes without backend/API changes. | HeroUI official docs, Pencil/Figma evidence, visual inspection metrics, component graph audit. |
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. |
debug-fix |
Bug, failed test, broken build, regression, or unexpected behavior. | Root-cause investigation, failing regression test, targeted fix, fresh verification. |
Superpowers Execution Handoff
After the implementation plan passes this skill, attach this handoff:
superpowers:test-driven-development: production code requires a previously observed failing test.superpowers:subagent-driven-development: default for independent tasks; use one fresh implementer and one reviewer per task.superpowers:executing-plans: fallback only when subagents are unavailable or tasks are tightly coupled.superpowers:requesting-code-review: required after each substantial task and before final completion.superpowers:verification-before-completion: fresh evidence before any completion claim.superpowers:finishing-a-development-branch: structured branch finish after tests pass.
Required execution artifacts: task brief, task report, review package, .superpowers/sdd/progress.md, final code review report, and final acceptance report.
Next Gate
implementation-in-progressmay start only after the implementation plan artifact passes review, a flow profile is selected, and the Superpowers execution handoff is attached.
04 同仓库更多 Skills
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.
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.
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.
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.
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.
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.