review-design

To review a design proposal, load required context resources and apply role-aligned feedback to highlight assumptions, gaps, and risks. This process ensures structured critique during early design phases by appending a Review Log with actionable feedback while preserving the original document content for traceability.

The best way to add feedback to a draft design document while preserving original content is appending a Review Log entry. This method attaches actionable feedback and open questions directly into the proposal, maintaining full traceability of revisions and ensuring the base draft remains intact.

Yes, you can critique an SDLC design proposal using role-specific context. The review process loads frontmatter-defined role context to tailor feedback, ensuring the structured critique aligns with specific reviewer perspectives and accurately surfaces relevant gaps, assumptions, and risks.

A structured design review improves the software development lifecycle by surfacing gaps, risks, and actionable improvements before implementation begins. Conducting early reviews of draft proposals ensures assumptions are challenged and open questions are documented, reducing costly downstream errors.