planning-methodology

Minimal-change planning identifies the smallest set of code modifications needed by prioritizing file extension over modification and new files over existing ones. This approach reduces risk by limiting scope, making rollback simpler and verification faster. Start by analyzing your codebase structure, then decompose the feature into surgical changes with explicit verification steps for each.

Reversible planning enforces that every change includes an executable rollback procedure—typically a `git revert` command—before implementation begins. This ensures you can undo changes immediately if issues arise. The methodology assesses breaking changes, performance impact, and security risks upfront, then sequences changes to maintain system stability throughout.

Risk assessment maps potential failures across breaking changes, performance degradation, and security exposure for each modification. Rollback planning creates step-by-step undo procedures tied to specific changes. Together they form a comprehensive contingency strategy, allowing developers to execute with confidence and respond quickly if verification detects problems.

Yes. This methodology applies to research-to-blueprint transitions, feature decomposition, and verification-driven planning. It enforces Simplicity, Minimal Changes, Reversibility, and Verification constraints, delivering a Codebase Profile, Minimal Change Strategy, Risk Assessment, and Implementation Sequence—suitable for both tactical changes and strategic architectural work.

Use surgical planning when changes must be auditable, reversible, or operate under strict safety constraints—critical systems, shared infrastructure, or high-stakes features. The methodology prevents complex, irreversible implementations by enforcing clarity and safety before code is written, reducing costly rework and production incidents.

The methodology delivers four artifacts: a Codebase Profile (current state and dependencies), a Minimal Change Strategy (smallest required modifications), a Risk Assessment (potential failures and mitigation), and an Implementation Sequence (step-by-step execution order with verification methods and rollback commands).