One project, from first sentence to feature file.
Follow a leave desk for HR through one week with Speclr. In every phase, an answer from the team comes in and the spec takes its next shape.



Discovery · Vision Statement
Leave desk
Input

Employees should report sick leave in two clicks, and HR should never chase anyone for it.
Speclr asks back, and the Vision Statement fills section by section.
Day 1 · DiscoveryOne sentence becomes a product vision, one answer at a time.
Day 1 · Discovery
A sentence becomes a product vision.
Anna, the product owner, starts with one sentence: employees should report sick leave in two clicks. Steve from HR joins the interview. Speclr asks what a good analyst asks first, and the Vision Statement fills section by section next to the chat. Before anyone commits, Forge Idea pushes back.
Who has to know about a sick report today, and what goes wrong when they find out late?

Team leads plan around it, and payroll needs every report before the 20th.
Discovery interview
Discovery · Vision Statement
Leave desk
Day 2 · Exploration
The whole product on one map.
Anna and Jonas build the story map with Speclr: chat on the left, map on the right. Activities run from left to right, the stories sit underneath, and gaps show up as holes while they are still cheap to fill. Everyone sees the same map, so nobody works from an outdated copy.

Team leads plan with a shared calendar, not with a list from HR.
Then “See who is out” needs a story of its own. Should the team lead be notified as well?
Exploration interview
Day 3 · Planning
Slice it, and name the risks.
Anna drags stories into milestones and parks the rest in the icebox. Speclr asks what has to ship first and what could break the plan. Each risk gets a probability, an impact and a mitigation, and a risk can become a story of its own. Scope discussions get easier when the trade-offs are visible.
The MVP stores sick notes, but no story says who may open them. How do you want to handle it?

Pull the story for opening sick notes into the MVP.
Planning · Milestones
Risk register
No open risks yet
Week 2 · Refinement
Every story ends in scenarios.
Story by story, Speclr runs a 3 Amigos style interview: Anna for the business, Jonas for the build, Steve for the domain. Rules, flows, data and quality get covered. Five reviewers read along and raise findings in the same conversation, while changes are still cheap. The Project Constitution applies to every story without anyone repeating it.

From the fourth day, a sick note is required, and only HR may open it.
Noted as BR-033 and BR-034. Two reviewers have a point about this story.
US-021 · Absence
Report sick leave
Business Rules
Scenarios


Hand-off
Plain files, any agent.
When the stories are ready, Speclr exports a Markdown mini-PRD and one .feature file per story. Jonas commits them next to the code and uses them as acceptance tests and as his agent’s definition of done. Stories become issues, and the documentation becomes pages in the wiki the team already uses.

I point my coding agent at the features folder, and it builds against the scenarios.
What carried through
Nobody explained the leave desk twice.
Every answer in every chapter went into the project context. Each new question started from what Speclr already knew.
Domain Knowledge
Glossary, regulations and notes as PDF, Markdown or text. Agents add what they learn, and every new answer is checked against it.
Project Memory
Who the users are, what was decided, what is out of scope. Every later session starts from the same facts.
Project Constitution
Constraints set once, for example “no diagnosis data is stored”. They show up in the scenarios of every story.
After Discovery: the problem, the users and the first rules are known.
