Tools · Software engineering
Requirements
Paste an idea (or book, study, report) — get a PRD-grade, MVP-scoped backlog.
How it works
Two LLM passes: source-specific extract, then one strict normalize pass for every variant; typed/prioritized requirements with user stories + acceptance criteria; honest gap report on what's missing or thin.
You bring
{ input, sourceType: business_idea|deep_research|book|research, sourceId? }
You get
RequirementCanonical[] + gap report (missing/weak fields)
Use it for
- →Storefront intake step 1: client idea → scoped backlog in one round-trip (scoping becomes a config call, not a workshop)
- →Turn a portfolio product idea into a PA-NNN-ready build plan
- →Pair with application-designs for the full 'brief → buildable spec' deliverable
See it work
example outputSource: a one-paragraph product idea for an internal employee-referral tracking tool (sourceType: business_idea).
Requirements — Employee-Referral Tracker (MVP-scoped)
A PRD-grade backlog extracted from the idea, normalized and prioritized. 6 requirements; gap report below.
REQ-001 · Submit a referral (functional · must-have · phase1)
- User story: As an employee, I want to submit a candidate referral with the role and a resume, so that I'm credited if they're hired.
- Acceptance criteria: Form captures candidate name, email, target role, file upload; duplicate (same email+role) is blocked; submitter sees a confirmation with a tracking ID.
- Effort: small · Complexity: low
REQ-002 · Track referral status (functional · must-have · phase1)
- User story: As an employee, I want to see my referral's stage (submitted → screening → interview → hired/closed), so that I know where it stands.
- Acceptance criteria: Status visible to the submitter; updates timestamped; closed referrals show a reason.
REQ-003 · Recruiter review queue (functional · must-have · phase1)
- User story: As a recruiter, I want a queue of incoming referrals, so that I can action them without email.
REQ-004 · Bonus eligibility rules (business · should-have · phase2)
- Configurable payout amount and the tenure threshold that triggers eligibility.
REQ-005 · Role-based access (non-functional · must-have · phase1)
- Employees see only their own referrals; recruiters see all; HR admin manages rules.
REQ-006 · Notifications (user_experience · nice-to-have · phase3)
- Email/Slack on status change.
Gap report
- Missing required fields: REQ-004 — no acceptance criteria yet; REQ-006 — no owner/persona specified.
- Weak fields: REQ-003 description is thin (queue sorting/filtering rules unspecified); no requirement covers reporting/analytics, though the idea implies tracking conversion rates — flagged, not invented.
Run it on your data
Call it on your own inputs — over the API, or hand it to your AI agent via MCP. Discovery is open; running it is metered.