Pmx Requirements Definition

Define functional and non-functional requirements clearly.

giljae Updated

File contents

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

  1. Clarify the goal, user, or decision context.
  2. Use the skill-specific lens below to structure the work.
  3. Make assumptions explicit instead of hiding them.
  4. End with a practical recommendation or next step.

Skill-specific lens

  1. Start from user outcome and system behavior.
  2. Separate must-haves from nice-to-haves.
  3. Cover constraints, edge cases, and quality attributes.
  4. Note assumptions and unresolved decisions.

Output

  • Functional requirements
  • Non-functional requirements
  • Constraints
  • Open questions

giljae/pmx-skills-gemini/tree/main/skills/pmx-requirements-definition commit 8ccf2e0542

Frequently asked questions

npx skillmds@latest add giljae/pmx-requirements-definition