Open source · Apache-2.0 · on PyPI
Requirements discovery, from a vague request to a decision brief.
Find what could change the solution before you commit to the scope.
Paste a client or stakeholder request. Requivo names the assumptions and missing decisions that could change the workflow, integrations, permissions, timeline or effort — then writes the brief, or a PRD, from the model you validated. When an answer changes later, it computes exactly what that breaks.
For the people who own scoping — solutions engineers, technical PMs, consultants — and the stakeholders they hand the brief to.
uvx --from "requivo[web,anthropic]" requivo webOpens Requivo Web at http://127.0.0.1:8765. Nothing installed — uv fetches it into a temporary environment. Set ANTHROPIC_API_KEY to analyse a new request.
No key yet? uvx --from requivo requivo demo replays a full run — offline, in your terminal. Analysis runs on your own Anthropic key: a full discovery typically costs well under a dollar.
Local-first · sessions never leave your machine · no accounts, no database
Replace the email and spreadsheet leave process with a configurable, auditable approval workflow.
“We’d like to set up a leave approval system.”
What Requivo understood
Leave is approved inconsistently today — email and a spreadsheet, no systematic balance check, no audit trail.
What we are assuming
- French labour law is one country template among others
- No payroll integration at this stage; calendar sync is one-way
What could change the solution
- Do the new system and the existing HR tool both stay live during the pilot?
Why it matters— Two-way sync brings reconciliation rules, conflict handling and an ownership rule per field. A one-time migration brings none of them.
Likely impact: Integrations & notifications - Who can cancel leave that has already started?
Why it matters— Decides whether cancellation is a state change or a separate HR-validated flow.
Likely impact: Permissions
See it run
Not a mockup. A recording.
One request, typed as a stakeholder would send it, through to the decision brief — captured from Requivo Web running on a laptop.
“We'd like managers to approve employee leave requests, with an escalation if the manager is away.”
13 seconds · no sound · nothing sped past the parts that matter
The difference
One request, two ways to treat it.
An LLM will happily turn a half-understood request into a polished PRD. Clean documentation is not the same as a correct understanding — and the expensive mistakes come from the question nobody thought to ask.
Generic AI
Requivo
The decision rule is information value = uncertainty × impact. Impact is estimated from the product context you give it, so better context means sharper questions.
How it works
Understanding first. Documents second.
The shared understanding is the source of truth. Every document is generated from it — and stays tied to the reasoning behind it.
Bring a request
A sentence or a rambling email — a symptom, not a spec. Nothing is established yet.
Clarify what matters
Requivo asks only what would change the solution, and infers the rest as assumptions to confirm.
Validate the understanding
Your answers land in a versioned, typed model — the durable product, not a transcript.
Generate documents
Each one is a view of that model, and knows which decisions it rests on.
what we know what we are assuming open question
The main output
A decision brief — the smallest document a scope review can be run from.
What is confirmed, what is assumed, the decisions on record, the premises worth contesting, and what is still open. It is not a PRD; it is what you read before writing one.
requivo estimate reads the same model and prints per-task ranges — wide where the understanding is still assuming, tight where it is confirmed. An analysis you read, not a document it saves.
The part a chat transcript cannot do
Change one answer. See what it costs.
Because Requivo keeps the understanding rather than just the answer, it can say what a changed answer moves — read off the dependency graph, not off a model’s opinion. The same change produces the same list every time, which is exactly what a generated answer cannot promise.
The answer that changed
“Correction: the migration is one-time. After cutover the legacy system becomes read-only — nothing writes back to it.”
Nothing is regenerated on your behalf. Requivo reports; you decide what to redo.
What changed
One part of the solution moved: Integrations & notifications.
Needs review
- Two-way synchronization during the pilot— decision
- Balances must reconcile on both sides— assumption
- Decision brief— document
Documents
It no longer matches the understanding it was generated from.
The same query runs before you spend anything — requivo impact <slug> integrations answers it from the dependency graph, with no provider call.
Architecture
Three ways in. One understanding.
Every interface uses the same session format and the same validated apply path — there is no fork, and no interface holds business logic of its own. They differ in weight, not in what they can reach.
The product
Requivo Web
A local browser workspace, and the way to use Requivo. Paste a request, answer the few questions that could change the solution, see what each answer moved. Set ANTHROPIC_API_KEY to analyse; without it the interface still opens and reads existing sessions.
requivo webAn integration
Requivo for Claude Code
Reasoning runs in the Claude Code session you already have, so there is nothing to configure.
/requivo:discover <request>Infrastructure
Requivo CLI
For automation and anything you drive from a script or a pipeline.
requivo discover | status | briefRequivo Core
The validated, versioned understanding. Provider-independent — no LLM, no network.
Requivo for Claude Code
Reasoning runs in the session you already have.
The skills read the request and the product context, reason in this Claude Code session, and pipe a structured proposal into the deterministic requivo CLI, which validates it, versions it and tracks what rests on what. There is nothing to configure — no API key, no model choice, no endpoint.
The arc — six commands, in the order they are usually reached
- 1
/requivo:discover <the request>Paste the request in whatever shape it arrived. You get the first structured read: what it states outright, what Requivo inferred and marked as an assumption, what is genuinely unknown, and the few questions whose answers would change the solution.
- 2
/requivo:status <slug>local readWhere it stands — readiness, what is still blocking, which documents have gone stale.
- 3
/requivo:answer <slug>Bring back what the client said. The answers are folded in, validated and applied as a new revision, and you are told what moved and what that made stale.
- 4
/requivo:brief <slug>The decision brief: what a reviewer needs before estimating or committing to scope. Saved, and tied to the revision it was written from.
- 5
/requivo:prd <slug>A PRD from the same model, with the unknowns still visible and the open decisions still open. Also saved and tracked.
- 6
/requivo:impact <slug> [topics]local readBefore you change an answer, what that change would reach: the decisions to re-validate and the documents to regenerate, read off the dependency graph.
Every command after the first takes the session slug, which /requivo:discover reports when it creates the session. The four that reason spend this session’s context window; the two local reads call the CLI and print what it computed. None of the six calls an API.
Two installs, and you need both
The plugin adds the six skills. The requivo CLI is the deterministic engine every skill drives.
/plugin marketplace add jbkkz/requivo /plugin install requivo@requivo /reload-plugins
uv tool install requivo
Not the requivo[anthropic] extra — that is for the optional standalone mode this plugin does not use. Then run requivo doctor; it reports a missing SDK or API key as informational, which here is the expected state.
The idea
Kept, not transcribed.
The understanding survives the session. A decision made three weeks ago is still on the record, with the reasoning that produced it and everything that came to rest on it — so coming back to a request months later means reading a model, not re-reading a chat.
Hosted beta
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 what Requivo establishes, assumes and leaves open.
- Get the questions that would change the solution, ranked by what they would move.
- Generate a decision brief from the understanding you validated.
You don’t have to wait to use Requivo. The Web interface, the CLI and the Claude Code plugin are open source and run on your own machine today — uvx --from "requivo[web,anthropic]" requivo web, with your own ANTHROPIC_API_KEY for the analysis. No key? uvx --from requivo requivo demo replays a real run offline. The waitlist is for a hosted version, which is still in development.