Free · no sign-up
Is this request ready to plan?
A request is decidable when it says what should change, plus who it affects or why now. Paste one — a Slack message, an email, a leadership ask — and see which of the three it actually states, plus the questions to send back for the rest.
Nothing is stored on our side. The text is sent to Anthropic's API for this one check.
What the check looks for
Most requests arrive as a topic ("mobile checkout"), a solution ("we need SSO") or half a sentence from a meeting. None of those can be planned, sized or refused honestly, because nobody yet knows what has to be different afterwards. The check reads the text you paste for three things and quotes back what it found:
- The need. What should change, or what problem exists — stated apart from the proposed solution.
- The impact. Who is affected, and what happens if nothing changes.
- Why now. The deadline, event or pressure behind the ask.
A request that states the need plus either of the other two is enough to start shaping. One that states none is a topic, and the useful reply is a question, not an estimate — which is why the check returns the questions to send back rather than a score.
What to do with the result
"Copy as a reply" puts the questions in a short message you can paste straight back to the requester. If the same gaps keep coming back, the fix is at the door: a request form that asks for the need, the impact and the trigger up front. The reasoning behind the three questions is in A topic is not a request, the terms are defined under intake, and the example one-pager shows what a request looks like once it has been shaped.
The check is limited to a few requests an hour. Nothing you paste is stored on our servers. No request to hand? Play eight example rounds instead, or print the one-page guide for the team.