ulw-plan

To turn a vague codebase change request into an actionable work plan, you need an explore-first approach that grounds the request in the repository, tracks assumptions, and separates discoverable facts from user decisions before finalizing.

Approval-gated planning for multi-module refactors is a process that records open questions, scope boundaries, and assumptions before finalizing a plan, ensuring implementation starts only after explicit approval and decision completeness.

Planning an architecture change that requires codebase exploration involves searching for real constraints within the repository first, then producing a structured plan with dependencies and executable verification criteria for each task.

Yes, this planning approach works for bootstrap planning in an existing codebase by requiring repository grounding to identify real constraints, tracking assumptions, and generating agent-executable acceptance criteria.

The best way to ensure a refactor plan is execution-ready for an agent is to produce a structured plan that includes explicit dependencies, verification steps, and agent-executable acceptance criteria for every task.

You should not use a decision-complete work plan for an engineering request when the change is trivial, requires no codebase exploration, or lacks the need for approval gating and executable verification criteria.