Start with the idea
Describe the problem and the change you want your software to make. You do not need technical language.
A temporary name is fine.
Who is it for?
A clear first audience makes it easier to choose which features matter.
Map the main workflows
Think about the jobs users need to complete. Add one action or workflow per line.
These become the main workflows for the first version. Keep them focused on outcomes.
Choose the MVP features
An MVP is the smallest useful version that solves the main problem. Add features, then classify each one.
Requirements and constraints
These answers help identify complexity early. Choose “Not sure yet” wherever you need to.
Define success
Describe what the first version must do to be useful. These criteria help a developer or AI check the result.
Review your project
Check the summary before generating your files. You can go back to any step to make changes.
The files will distinguish your answers from assumptions and unresolved questions. They are planning documents, not a guarantee of cost, feasibility or security.