plan-eng-review

Structure an engineering plan review by guiding scope definition, architecture discussion, risk assessment, and decision logging. This enforces a disciplined review flow with explicit criteria, ASCII diagrams, and artifact generation to support audits.

Document engineering decisions and tradeoffs using built-in tradeoff logging and decision-record generation. These artifacts accompany PRs or design docs, capturing assumptions and risks to ensure traceability.

Yes, you can use ASCII diagrams to visualize data-flow and edge cases during a code review. Built-in architecture and data-flow checklists surface risks early, while diagrams document decisions for future audits.

Facilitate an async engineering plan review using collaborative prompts that drive productive discussions. The structured Scope Challenge aligns goals and constraints, ensuring consistent documentation across distributed participants.

This engineering plan review framework works for both feature upgrades and large architectural rewrites. It applies a consistent, decision-focused workflow that captures assumptions, tradeoffs, and risks across any scale.

Avoid a structured engineering plan review workflow for trivial changes requiring no architecture discussion or risk assessment. The framework enforces a disciplined flow with explicit criteria, adding overhead to simple updates.