omk-plan-first

To create a safe read-only plan before refactoring code, enforce planning-only rules that clarify the goal, identify affected files, define implementation steps, and establish a rollback strategy. This prevents risky edits by resolving unknowns beforehand.

A read-only plan in software architecture is a pre-implementation workflow that structures risk-aware execution by specifying impacted modules, defining quality gates, and establishing acceptance criteria. It ensures implementation remains predictable without modifying files.

Defining acceptance criteria for a risky multi-file change requires creating a structured pre-implementation plan that explicitly checks what done means. This limits blocking questions and enforces quality gates to ensure the change meets success criteria.

You need to use a planning workflow for feature development when facing ambiguous tasks that require clarification, risky edits, or architecture work. It produces a safe plan identifying unknowns, affected modules, and a rollback strategy.

The best way to manage risk during code refactoring is to produce a risk-aware execution setup that identifies unknowns, specifies affected files, defines quality gates, and establishes a rollback strategy. This makes implementation predictable.