Open-source requirements reasoning
Turn vague requests into validated product decisions.
Requivo separates facts, assumptions and unknowns, asks the questions that could change the solution, and keeps the resulting decisions traceable.
Open source · Local-first · CLI, Claude Code & Web
Request
“An app for field technicians to see jobs, log hours, track van stock and work offline.”
Model
- FACTTechnicians receive jobs from a dispatcher.
- FACTConnectivity is unreliable in the field.
- ASSUMJobs already exist in a scheduling system.
- ASSUMA two-month pilot can include every integration.
- UNKWNWhere jobs originate.
- UNKWNOffline conflict rules.
Priority questions
- ?Where do jobs originate and who assigns them?
- ?Which actions must work fully offline?
Readiness
3 / 6 resolvedDecision revealed
Offline conflicts need an explicit resolution rule before any sync is built.
One request, two ways to treat it.
Generic AI
Requivo
Worked example
The same request, read closely.
A field-service brief looks simple. The risk is in what it quietly assumes.
“We need an app for field technicians to see their jobs, log hours, track van stock and work offline.”
Three questions that change the build
- 01
Where do jobs originate and who assigns them?
Decides whether Requivo is scheduling work or only displaying it.
- 02
What actually defines job completion?
Changes payroll, stock reconciliation and sign-off.
- 03
Which integrations genuinely fit the pilot deadline?
Separates the two-month pilot from the full rollout.
Decision revealed
If jobs do not already originate in a scheduling system, the pilot also needs a dispatch interface.
scope +1One unanswered question adds an entire interface to the two-month pilot.
Understanding first. Documents second.
Clarify
Find what could change the solution before you specify it.
Model
Facts, assumptions, decisions and dependencies stay structured and traceable.
Generate
Produce assessments, PRDs and delivery artifacts from the same validated model.
Use Requivo where you work.
Same Core. Same session model. Different interfaces.
- Requivo CLILocal and scriptable workflows.Commands and files.
- Requivo for Claude CodeInside the Claude session you already have.Reasoning and dialogue.
- Requivo WebA browser interface, run locally.Visual model, same Core.
The idea
The model is the product.
Documents are views of that model.
Requivo keeps one structured model of the requirement. Documents are generated from it — and stay tied to the reasoning behind them.
Persistence
The model persists across sessions, so decisions don't get lost in a thread.
Validation
Every assumption can be challenged and turned into an explicit decision.
Traceability
Each document links back to the facts and decisions it came from.
Interested in a hosted Requivo Web beta?
Join the early access list. I’m looking for Product Managers, Business Analysts, Solutions Engineers and teams working with complex B2B requirements.
- Bring a real request and see it split into facts, assumptions and unknowns.
- Get the priority questions that could change the solution.
- Generate a first solution assessment from the validated model.
The Core, CLI and Claude Code integration are open source today. The hosted Web version is still in development — early testers will be invited progressively.