Plan Review

Review product, business, and engineering decisions before implementation. Clarify unresolved requirements or critique a settled proposal through constructive and adversarial lenses.

1. Clarification turns an unresolved plan into a decision record, then stress-tests it.
2. Settled-decision critique challenges an existing decision or artifact without reopening choices that evidence does not invalidate.

Use both lenses by default: identify who benefits, who pays, what becomes hard to undo, and the constraint that preserves the useful upside. Honor an explicit Jekyll-only or Hyde-only request while still naming cost bearers, reversibility, and a concrete next step.

When to use

• Clarify a feature, infrastructure, architecture, product, business, or fiction plan before building.
• Challenge a settled strategy, roadmap, pricing, platform, governance, or design decision.
• Pressure-test assumptions, failure paths, incentives, reversibility, and second-order effects.

When NOT to use