refactor-design-report

A refactor design report converts architecture review findings into a code-grounded design document by aggregating identified problems, outlining target backend and frontend changes, validation strategy, implementation order, and acceptance criteria into a durable engineering report.

A refactor report should include target semantics, required backend and frontend changes, validation strategies, implementation order, acceptance criteria, and rollback and rollout guidance, all grounded in current code and contracts.

Document API and UI mismatches by grounding the refactor design report in current code and contracts, then outlining target models, required changes, validation strategies, and implementation order to produce a testable design.

Yes, the refactor design report supports optional persistence, writing the generated design document to the appropriate docs location, or otherwise presenting the complete report directly in the reply.

Yes, the refactor design report applies to bugs, API and UI mismatches, design gaps, and feature requests across both backend and frontend contexts, turning them into a durable, testable design with rollout guidance.

Refactor design reports depend on accurate identification of technical problems and product gaps beforehand, and require grounding in existing code and contracts to produce a testable design with meaningful validation and acceptance criteria.