Your build starts here
Replace bracketed details with your own goal, context, and checks. Keep the first build small enough to inspect.
Review this feature plan: [plan]. The approved requirements and acceptance criteria are [criteria]. The current implementation facts available for review are [facts and references].
Limit the review to violations of those criteria, unsupported technical assumptions, and missing failure behavior that affects the requested journey. For each actionable finding, cite the relevant plan passage or supplied fact, describe the triggering condition, and explain the practical consequence. Separate confirmed issues from questions. Return no findings when the evidence does not support one.
Propose a focused revision for supported findings, preserving the intended scope. After that revision, perform one check against the same criteria and state unresolved gaps. Do not keep adding preferences or new features to prolong the review.
Provide concise rationales and checkable evidence. A critique is not proof that the implemented feature works; name the execution or manual checks still required.Make this prompt yours
Use when the artifact and criteria are concrete. Resolve unclear requirements before turning disagreement into an automated quality score.
You might also hear
- constrained critique
- bounded plan review
- evidence-based review
The docs behind it
These references explain the underlying concepts and APIs. The prompt templates and project plans are original examples to adapt to your own setup.
Research sources reviewed .
Editorial review · October 28, 2026
Supported: Original, unexecuted critique template. Evidence-linked findings, fixed criteria, and no invented defect quota are sound review design; provider evaluation guidance does not guarantee this prompt's effectiveness.