Requirements Definition
When to use
- Use when the task clearly matches this PM activity.
- Use when a structured answer is more useful than a generic brainstorm.
- Use when the user needs explicit trade-offs, implications, or next steps.
Instructions
- Clarify the goal, user, or decision context.
- Use the skill-specific lens below to structure the work.
- Make assumptions explicit instead of hiding them.
- End with a practical recommendation or next step.
Skill-specific lens
- Start from user outcome and system behavior.
- Separate must-haves from nice-to-haves.
- Cover constraints, edge cases, and quality attributes.
- Note assumptions and unresolved decisions.
Output
- Functional requirements
- Non-functional requirements
- Constraints
- Open questions