AI Spec & PRD Generator
Turn a paragraph into a complete PRD, technical design, or API spec, with built-in checks for ambiguity, testability, and completeness.
Core templates and the lint are free. No card.
Shoppers keep losing their carts when they switch from phone to laptop. Let signed-in shoppers save a cart and pick it up on any device. It should be fast, carts should expire after a while, and we may email a reminder before they do.
Saved carts
Signed-in shoppers lose their cart when they move between devices, so they rebuild it by hand or give up.
Save the cart to the shopper's account. A signed-in shopper's cart to their account within 2 seconds of any change.
Restore the cart on any device. When the shopper signs in on another device, the app restores their saved cart within 2 seconds and merges any items already in that device's cart.
Expire saved carts. Saved carts expire after time, and the shopper sees which items .
Remind before a cart expires. The system email the shopper a reminder a days before their cart expires.
cart sync. Cart sync feels on mobile networks.
Guest carts · Sharing a cart with someone else · Price changes on saved items
0.4 × 80 lint + 0.4 × 40 coverage
+ 0.2 × 100 structure (3 of 3) = 68
2 of 5 covered = 40% coverage
Cart follows the shopper
Most features start as a paragraph in a ticket. The gaps in it show up in code review, or in production, when they cost the most to close. Shivo turns that paragraph into a spec your team can build from, and points at every sentence an engineer would have to guess at, before anyone writes a line.
Where a vague sentence gets caught
01In the spec
One sentence changes before anyone builds on it.
Shivo flags it here
02In code review
The pull request is reworked, then reviewed again.
03In production
A fix ships after people have already hit the gap.
Pick the document
Choose what you are writing and Shivo drafts every section of it from your paragraph. Flip through the outlines it writes to.
Define the problem, goals, users, and measurable requirements for a product or feature before a line of code is written.
10 sections, each drafted from your paragraph and linted.
01 / 06: Product Requirements Document
Every requirement, traced
Shivo links every requirement to its Given, When, Then scenarios and marks what no scenario verifies yet. Pick a spec to see its map.
specs/saved-carts.md · 2 of 5 covered
40%coverage
Save the cart to the shopper's account
Cart saves after a change
Restore the cart on any device
Cart follows the shopper
Carts merge without duplicates
Expire saved carts
Criteria exist, but the requirement is ambiguous and cannot be firmly verified.
Lint 65someshouldno measure
Expired cart explains itself
Remind before a cart expires
No acceptance criteria linked to this requirement.
Lint 66fewmayno measure
Gap
No Given, When, Then proves FR-4 yet. Shivo lists it here instead of letting it ship untested.
Fast cart sync
No acceptance criteria linked to this requirement.
Lint 68fastno measure
Gap
No Given, When, Then proves NFR-1 yet. Shivo lists it here instead of letting it ship untested.
Review that converges
Route the spec to a reviewer, argue in one thread and see exactly what changed between versions. Each version is scored, so the thread ends when the spec is ready.
Review thread
In reviewCompleteness by version
Almost ready
Try both paths: approve now, or ask for changes first.
Pricing
Draft and lint for free. Pro adds the acceptance-criteria generator, the review workflow and saved history. Teams that need single sign-on or self-hosting talk to us.
Get started
$0forever
For product and engineering teams
$15per month
For organizations
Custom
Shivo turns a plain-English idea into a structured spec, including PRDs, technical design docs, RFCs, security specs, and one-pagers. It also lints requirements for ambiguity, testability, and completeness, generates Gherkin acceptance criteria, and supports a full review workflow with version diffs.
Every requirement is scored for ambiguity, testability, and completeness, and Shivo flags the specific issues to fix. It also generates acceptance criteria so each requirement has a clear, testable definition of done, which catches vague or incomplete specs before engineering starts.
Yes. Specs are fully editable, and you can route them for review, collect approvals or change requests through a comment thread, and compare what changed between versions with a side-by-side diff. Finished specs export to Markdown.
Your specs, requirements, and comments are scoped to your account and encrypted at rest, and we never use your content to train models.
The Free plan lets you generate specs from core templates and lint requirements with no credit card. Pro is $15 per month for unlimited generation, all templates, the acceptance-criteria generator, the review workflow, version diffs, Markdown export, and saved history. Enterprise is custom-priced with SSO, a self-host option, and dedicated support.
Vague words such as fast, easy, secure or some; non-committal wording such as should, may or might; passive voice that hides who acts; requirements with no number, threshold or pass/fail condition; descriptions too thin to build from; and requirements with no clear subject. Each finding names the words that triggered it.
Three parts: the mean lint score of the requirements, the share of requirements fully covered by acceptance criteria, and the share of structure checks passed (a problem statement, measurable goals and an out-of-scope list). Completeness is 0.4 × lint + 0.4 × coverage + 0.2 × structure. The criteria sheet at the top of this page shows the math for each sample.
Yes. Try the demo from the sign-in page: it opens a seeded workspace with specs, requirements, reviews and templates, with no account and no API key.
Your next feature
Paste a paragraph and get a PRD, its lint findings and acceptance criteria for every requirement. Core templates and the lint are free, with no credit card.
