Document generators
User story and acceptance criteria generator
A feature list like "admin panel" cannot be costed, because everyone reads it differently. A story with a role, a reason and acceptance criteria can be costed, because it states plainly when the work is done. This generator walks you through that format and makes sure no story is left without criteria.
Free · no signup · runs in your browser
E.g. "Order handling" or "Customer portal".
Story 1
Who needs this. A specific role, not "user".
An action, not a screen. "I want to export the order list", not "I want a button".
The reason. If it is hard to write, the story may be unnecessary.
One per line. Ideally: Given ... / When ... / Then ...
Preview
# User stories and acceptance criteria **Epic or module name:** Untitled ## 1. Untitled **Must** > As a _to be filled in_, I want _to be filled in_, so that _to be filled in_. **Acceptance criteria** _no criteria defined - the vendor will not know when this is done_ ## Summary Must: 1 · Should: 0 · Could: 0 · Won't: 0 --- _Document generated with a free tool by Exmoor Software (exmoor.pl/en/tools). The content belongs entirely to its author._
Got your list of stories?
This is the best moment for a quote - with stories and acceptance criteria the scope can be costed without guesswork. A ballpark instantly, a reply from a human within 24 hours.
Estimate your project in 2 minHow it works
- 01
Add stories
Each in the format: as a (role) I want (action) so that (reason). The role should be specific and the action described without referring to screens.
- 02
Set MoSCoW priorities
Must, Should, Could, Won't. Deliberately marking something Won't is as valuable as Must - it is what protects the budget of the first version.
- 03
Write acceptance criteria
One per line, ideally given/when/then. A story with no criteria is clearly flagged in the document.
Assumptions and limits
- A story describes a need, not a solution. "I want an export button" is interface design; "I want to export this month's orders to a spreadsheet" is a need a vendor may solve better than you assumed.
- If the "so that" field is hard to fill in, it is often a sign the story is not needed. This is the cheapest moment to notice that.
- Acceptance criteria are what let work be accepted without argument. Their absence is the most common cause of "it was supposed to work differently" conversations at the end of a project.
- The document comes out as Markdown with checkboxes, so it pastes into Jira, Linear, Notion or GitHub Issues without losing structure.
- Everything is produced in your browser - we neither send nor store the content of your stories.
Frequently asked questions
How many stories do I need to get a quote? +
For a ballpark, a dozen of the most important ones marked Must is enough. For a firm quote you need the full Must and Should list - without it a vendor is pricing a scope they cannot see.
What is the difference between Should and Could? +
Should is important but not blocking - you can ship without it and add it in the next iteration. Could is something you build only if budget or time remains.
Do criteria have to be in given/when/then form? +
No, it is only a suggested structure. What matters is that a criterion is checkable: "the list loads in under 2 seconds with 10,000 records" is a criterion; "it should be fast" is not.
Can I paste the result into Jira? +
Yes. The document is Markdown with task lists, so the structure survives in Jira, Linear, Notion and GitHub Issues.
Related tools
All tools →Spec generator
Answer a dozen questions and download a ready Markdown brief that every vendor will read the same way.
RFP generator
Assemble a request for proposal with selection criteria, contract terms and process rules.
Integration cost
Estimate the effort and cost range of connecting an ERP, webshop, warehouse and accounting.
Turn the numbers into a project
Get a ballpark instantly, a reply from a human within 24 hours and a firm quote after a short call. No obligation.
Estimate your project in 2 min