PRD

Create a structured Product Requirements Document with user stories, acceptance criteria, functional requirements, and scope boundaries.

When to Use

• A direction has been chosen and needs to be formalized into requirements
• Before architecture or task breakdown — requirements must exist first
• When the team needs a shared source of truth for what "done" means
• When acceptance criteria need to be explicit and verifiable

When NOT to use: Requirements are already documented in a prd.md that is still accurate, or the change is a single-line fix with obvious scope.

Input

• brainstorming.md from the artifact folder (required — contains chosen direction)
• goal-definition.md from the artifact folder (required — contains success criteria)
• context-map.md from the artifact folder (recommended — for technical grounding)