blade-plan

To plan a medium code refactor without scope creep, break the request into a concise plan with ordered tasks and a final summary. This structured workflow enforces minimal-scope changes and task-by-task context reloading to keep multi-file work aligned.

The best way to execute multi-file bug fixes in a single session is using a controlled execution sequence with task tracking. This approach requires context reloading for each task and build verification to catch issues early while maintaining alignment across files.

You should use a structured task breakdown for feature additions when the work affects several files but does not require a full design document. It applies to moderate-complexity tasks that can finish in one session, such as starter-module work.

To verify build checks during a moderate code change workflow, apply built-in validation steps that encourage build checks after ordered tasks. This catches issues early and ensures the multi-file changes remain focused and functional.

You should escalate medium code changes to a full design workflow when the complexity exceeds the guardrails of a single-session structured plan. If the multi-file refactor or feature addition cannot be broken into minimal-scope ordered tasks, it requires full design.