Requirements Product Management
Prompts
-
Product Requirements Document Skeleton With Example
Write a PRD that teams will use.
-
Acceptance Criteria Review
Make criteria testable and complete.
-
Edge Case Brainstorm for a Feature
Find what the happy path misses.
-
Non-Functional Requirements Checklist
Specify quality, not just features.
-
Feature Specification for Design and Engineering Handoff
Provide what designers and developers need.
-
User Flow Documentation
Describe the journey step by step.
-
MoSCoW Scope Negotiation
Cut scope with agreement.
-
Requirements Conflict Resolution
Resolve contradictory requests.
-
Beta Program Requirements and Exit Criteria
Run a beta with clear goals.
-
Requirements Traceability Matrix
Link needs to tests and releases.
-
Data Requirements and Dictionary for a Feature
Specify the data a feature needs.
-
Permissions and Roles Matrix Design
Define who can do what.
-
Error Messages and Microcopy Specification
Write helpful text for failure states.
-
Acceptance Test Scenarios From a Spec
Turn a spec into test cases.
-
Product Requirements Review Checklist
Check a PRD before engineering starts.
-
Product Requirements Document From Notes
Turn rough notes into a structured PRD.
-
Requirements Ambiguity Review
Find unclear or conflicting requirements.
-
User Story Mapping Session Plan
Plan a workshop to map the user journey.
-
Acceptance Criteria Generator
Write testable criteria for a story.
-
Edge Cases and Failure Modes Brainstorm
Think of what could go wrong.
-
Feature Spec for Engineers and Designers
Communicate a feature clearly to both.
No prompts match those filters.