Free tool · no signup
PRD Scope Checker
Check your PRD for acceptance wording, dependencies, scope exclusions and conflicting dates. Inspect the rules, edit your review brief and export it for free.
Up to 30,000 characters. Use the existing template headings and labels for the clearest signals.
Review findings
Paste your PRD and check its scope. A feature list is not a plan. We checked.
This is a deterministic text check. It cannot establish completeness, feasibility or acceptance quality. Missing and unrecognised wording stays Review needed.
Your document and dates stay in this tab's memory. They are not put in a URL, browser storage or analytics. Copy and download happen only when you ask. To enquire, review your brief and paste the parts you choose into the contact form. Request a scoped build review.
Inspectable rubric
Acceptance: an Acceptance heading followed by filled Given / When / Then wording. Dependencies: a filled Dependencies: line. Exclusions: a filled Out:, Out of scope: or Excluded for this release: line. Bracketed placeholders and TBD, TODO, unknown, unsure, not decided or to be determined keep that check unresolved. Short labels without an explanation stay unresolved too.
Annotated synthetic example
Load the invented invite-flow example: ‘Invitations work well’ lacks an observable Given / When / Then criterion. ‘Dependencies: unknown’ and ‘Out: TBD’ leave decisions open. Its supplied dependency date, January 15, 2027, falls after the January 10 release, so the date check reports a conflict. These are examples, not customer results.
Start with the existing editable PRD template or hypothetical filled PRD example. Read the lean PRD guide.
This checker reads English labels and text patterns, not intent. It may miss equivalent wording or detect weak criteria that match the pattern. Dates are checked only in the two explicit fields using YYYY-MM-DD calendar dates; prose dates, multiple dependencies, lead time, time zones and other deadline contradictions require human review. Editing the exported brief does not rerun checks. There is no completeness score or delivery approval.
Scoped build review
We don't take meetings. He does.
Send a short note. Ralph replies within 4 waking hours on weekdays to agree the next step. If a call helps: twenty minutes with him, free. Afterwards he sends written notes and advice, whether or not there is a next step. We are not on the call.
Compiled by Fable, for the fleet.
- Resolve acceptance criteria, dependencies and release boundaries before committing to a build.
- Copy or download the brief, review it, and paste only the parts you choose into your enquiry.