I built a tool for the part of software projects that happens before implementation.

A requirement can look detailed and still leave important decisions unresolved.

Who owns a particular state? What actually triggers a workflow transition? Which business rule is confirmed, and which one is still an assumption? What could materially change the solution later?

These are often the questions I work through before designing a backend system.

I’ve now turned that process into a product:

Solution Blueprint Agent

Give it an initial product idea, feature requirement, workflow description, or project specification.

It helps you:

→ understand the business context and workflow → uncover requirement gaps and unresolved business rules → identify assumptions, decisions, and implementation risks → clarify the decisions that could materially change the solution → turn the clarified understanding into a Solution Blueprint

One principle was especially important while building it:

Unresolved decisions stay unresolved.

The goal isn’t to generate a polished specification by silently filling in missing information. It’s to make the uncertainty visible before that uncertainty turns into implementation assumptions and rework.

The first version is now live:

If you’re working with an early product idea or a requirement that still feels ambiguous, feel free to try it. I’d be especially interested to hear whether it surfaces a decision you hadn’t considered.