| name | mvu-refactor-plan |
| description | Plan and implement CMake + elomaxz MVU refactors in C codebases. Use when user references elomaxz, MVU, CMake refactor plan, or attached implementation plan. |
MVU refactor (CMake + elomaxz)
When to use
- User attaches or references an implementation plan for CMake + elomaxz MVU
- Refactoring model/view/update structure in a C project
- Integrating patterns from the elomaxz library
Steps
- Read the attached plan and existing
CMakeLists.txt, model, and app entry points.
- Grep for symbols mentioned in the plan before moving files.
- Implement in small steps: CMake → headers →
.c → build after each logical chunk.
- Run build; fix compiler errors before next step.
- Update README/license only after core build passes.
Constraints
- Follow elomaxz naming and MVU boundaries from the plan — do not invent parallel architecture.
- Prefer minimal diffs; avoid drive-by reformat of unrelated C files.
- If ColumnLimit breaks signatures, fix layout in context — do not truncate identifiers.
Done when
Build succeeds and plan checklist items are addressed or explicitly deferred with reason.
Example provenance: premflow. Pair with explore-repo-readonly when structure is unknown.