plan-quality-gates

To prevent fabricated timelines, validate your plan to block calendar-based duration estimates unless explicit capacity data is provided. This removes vague timeline assumptions and enforces verifiable exit criteria at plan creation time.

Enforce dependency ordering in a product roadmap by requiring every phase to state explicit Depends on relationships. This ensures phase ordering and parallelism are clear and prevents hidden assumptions during execution.

Exit criteria are verifiable when they are concrete, objective "done means" statements that can be checked for each phase. Plan validation forces these measurable exit conditions instead of allowing vague completion metrics.

Yes, you can validate an existing phased migration plan by reviewing it to ensure each phase includes explicit Depends on relationships and measurable exit criteria. This flags unverifiable estimates and hidden assumptions.

You need to validate plan exit criteria and dependency ordering when drafting roadmaps or phased plans to reduce the risk of unrealistic commitments. It ensures no invented timelines or hidden assumptions cause delays before execution begins.