Pressure-tests an engineer's or team's estimate against the actual code and scope before a leader commits it upward — surfacing the hidden work, unstated assumptions, and risk the original number glosses over, and returning a revised range with a confidence level. Use when the user says "does this estimate look right", "sanity-check this timeline", "they said two weeks — is that real", or must commit a delivery date they didn't produce themselves. Use this to stress-test one estimate against reality — use capacity-planning for whole-team bandwidth math and sprint-planning-breakdown to slice an epic into estimated tickets.
