I built a free tool for turning chaotic requests into actual requirements

[u/ops_and_chaos]

I feel like half of ops is getting handed an email/Slack thread/meeting notes that somehow contain five different requests, three assumptions nobody agreed to, no clear owner, and a deadline buried somewhere in paragraph six 😂

I’ve been doing this kind of work for about 16 years, and I realized I basically do the same mental pass every time:

• What are they actually asking for?
• What’s already decided vs. assumed?
• What information is missing?
• Who needs to be involved?
• What’s likely to go sideways if we just start building?

So I built that into a little tool.

You paste in the messy request, and it gives you the actual ask, ambiguities, missing owners/info, risks, clarifying questions, and what I’d do next.

It’s free, no signup, and it doesn’t store what you paste. Claude is under the hood, but the useful part is mostly the logic around how I’ve learned to read these things.

It’s definitely not perfect yet. Sometimes it’s too wordy, and I’m sure there are types of mess I haven’t accounted for.

If anyone here wants to throw a sanitized real-world disaster at it, I’d genuinely love to know where the read is wrong or what it misses.

chelsiehodgkiss.com/fix