What problem does it solve? Code changes made without a plan lead to missed files, broken callers, and unverified "done" reports. This Skill forces a structured planning phase before any code is touched: requirements are confirmed through a one-question-at-a-time interview, the impact scope is measured with real commands, and the work is split into tasks that each carry files, acceptance criteria, and verification commands. ## Core Features & Use Cases - Requirements Interview: Confirms intent through single-question rounds with GUESS hypotheses until confidence reaches 95%, then restates the goal for explicit approval. - Command-Verified Impact Analysis: Every factual claim in the plan must come from an executed command recorded in an Investigation Log table. - Task Decomposition with Review: Splits work into T1/T2 tasks with Files, acceptance criteria, and verification commands, then runs a plan-reviewer subagent before user approval. - Use Case: When asked to "add a password-reset link and refactor the login flow," the Skill interviews the user, greps the codebase for affected callers, writes plan.md with verifiable tasks, gets approval, and hands off to the implement skill. ## Quick Start Ask the assistant to plan a multi-file code change, such as "plan adding a password reset feature to the login screen," and it will interview you, measure the impact scope, and produce an approvable plan.md.
