Claude / Documents, Data & Research
Claude: extract requirements without inventing acceptance criteria
Provide a specification with stable section labels. Decide whether recommendations and mandatory statements should be separated.
Environment and inputs: Claude user guide · Feature and source access depend on the active account, app and organization settings. Optional file or app steps have a text-excerpt fallback. No fixed model version, price or usage quota is assumed.
What you will make
A practical Claude guide to extract requirements without inventing acceptance criteria. Use the sample input and prompt, then check the result. Use a fictional support-document review as the practice setting. Keep passages and your interpretation in separate output fields.
Prepare the source and scope
Provide a specification with stable section labels. Decide whether recommendations and mandatory statements should be separated. Open Claude and start a focused conversation, or use the appropriate existing project for recurring work.
Try this prompt
In Claude, provide the prepared input, then send the following request. For real work, replace fictional details with approved facts.
Extract requirements into ID, Requirement, Source section and Testable evidence. Separate must from should. Mark an inferred test as Suggested, not part of the source.Review the result
Each mandatory statement should appear once and preserve its qualifiers and scope. Record each correction and its supporting source.
If the answer is wrong or incomplete
An assistant can turn an example into a requirement. Review modal verbs and check suggested tests with the product owner. Put the source excerpt and the request in separate labeled blocks. For longer reviews, retain paragraph labels so corrections remain traceable.
Practice and completion check
Repeat with one incomplete input. Check the answer against the review criteria, remove unsupported claims and save the prompt with its source version. This workflow has not been verified in a customer deployment.