Structured Impl Planner

Jumping straight to code works until step seven, where the change you didn't anticipate meets the four files you already modified and nothing fits together anymore. This skill forces the planning work that prevents mid-implementation pivots: it maps every affected module before you write a line, surfaces the dependency order that makes changes non-reversible, identifies the test harness you need to build first, and writes a sequenced task list where each step is independently mergeable. You get the full implementation plan — constraints, risks, rollback points — before you open an editor. Use it when the feature touches more than two files, when the spec is incomplete, or when your last three attempts at 'just implementing it' produced a mess you refactored for longer than you built. Give it your codebase context, the feature description, and the constraints that matter; it returns a plan you can execute without rediscovering the architecture mid-flight.