An internal subsystem has become messy, duplicated, or hard to extend, but external behavior should remain stable.
Example outcome:
- simplify the command router;
- preserve existing behavior;
- reduce future maintenance cost.
/wf.discover
/wf.spike
/wf.arch
/wf.spec
/wf.plan
/wf.tasks
/wf.tooling
/wf.dispatch
/wf.implement
/wf.review
/wf.finish-branch
/wf.human-qa
/wf.finish-report
- Refactors are architecture-sensitive even when user-facing scope is unchanged.
- The architecture and task stages help contain hidden expansion.
- Review should focus on equivalence, not just style.
- current pain map;
- target design sketch;
- invariants that must not change;
- migration or rewrite boundary;
- review checklist for parity.
Treat as governed work:
/wf.arch/wf.spec/wf.plan/wf.tasks/wf.tooling
- Router rewrites
- State-management cleanup
- Dispatch/runtime simplification