Product requirements & acceptance criteria
Turn research, business constraints, and product ideas into actionable requirements with clear boundaries, exceptions, and observable acceptance criteria.
Inputs
User problems, business goals, research evidence, existing systems, and resource constraints.
Deliverables
Requirements, user journeys, API outline, priorities, and acceptance cases.
Step-by-step workflow
Break the work into verifiable stages, then choose models and supporting tools.
- 01
Align goals and evidence
Connect requirements to real user problems, separating necessary outcomes from implementation preferences.
- 02
Define scope and boundaries
List main flows, exceptions, permissions, and explicitly excluded work.
- 03
Break down deliverables and interfaces
Create independently verifiable tasks and, where needed, API or data structure drafts.
- 04
Write acceptance cases
Use concrete inputs and expected results to make requirements testable, then obtain team review.
Required model capabilities
Combine models for the actual stages. The directory includes candidates matching one or more of these capabilities.
View matching modelsSupporting tools
Selection & delivery checks
- Use text reasoning for requirement structure and coding capabilities for interface and data drafts.
- Model-added assumptions are not user-approved requirements.
- Priorities must reflect business goals and real constraints.
An example request
Write product requirements from user research, design exception flows and acceptance criteria, draft APIs and data structures, and list assumptions requiring confirmation.Find models for this request