implementation-planner

To create an implementation plan, the Skill inspects your repository and asks targeted questions one at a time to resolve uncertainties. It then logs decisions and writes a structured, execution-ready plan to plan/{branchName}/{feature}.md.

The best way to prepare for handoff is generating a repository-grounded implementation plan with explicit scope, decisions, steps, validation, risks, and rollback guidance. This ensures the downstream agent can execute the feature without guessing hidden context.

Repository-aware planning works by inspecting the codebase, docs, tests, config, and nearby plans to ground decisions in real project evidence. It narrows uncertainty through one-question-at-a-time interrogation before finalizing the implementation steps.

Yes, you can use this planning approach for repository work requiring careful clarification, including bug fixes, feature delivery, and larger changes. It discovers the appropriate branch and interrogates requirements before writing the final plan.

You do not need to manually specify a branch beforehand. The planning process includes automatic branch discovery to identify the correct context, ensuring the final plan is saved to the correct plan/{branchName}/{feature}.md path.

Feature planning fails to account for hidden context when it skips repository inspection and decision logging. This Skill prevents that by interrogating requirements one question at a time and grounding every choice in real codebase, docs, and config evidence.