What problem does it solve? Non-trivial code changes often fail because implementation starts before anyone maps affected files, compares approaches, or surfaces hidden risks. This Skill enforces a discovery-first planning workflow so every refactor, feature, or reliability fix begins with a concrete, repository-grounded plan instead of assumptions. ## Core Features & Use Cases - Discovery-First Workflow: Inspects root docs, architecture documentation, agent context files, and affected modules before proposing anything. - Structured Output Contract: Produces a six-section plan covering problem statement, affected files, at least two options with trade-offs, a justified recommendation, a numbered implementation plan, and risks. - Planning-Only Discipline: Explicitly avoids writing code, premature abstraction, and single-solution bias. - Use Case: Before refactoring a cross-module authentication flow, run this Skill to map every touched file, compare two migration strategies, and get an ordered step list with rollback risks called out. ## Quick Start Ask the agent to plan the implementation of your feature or refactor before writing any code, and it will return a structured plan grounded in your repository.