PRD — key questions (clarification inventory)

Use when the user’s prompt is ambiguous. In chat, ask the smallest set that unblocks writing PRD_TEMPLATE.md — typically 3–5 questions, drawn from the areas below (do not run through all 12 as a questionnaire).

1. Name & Summary

   • What is the feature name? Provide a 1-2 sentence summary.

2. Problem Statement

   • What user problem does this solve? Who is affected?

3. Goals & Success Metrics

   • Primary goal (one sentence)
   • measurable success metrics (KPIs)

4. Non-Goals

   • What is explicitly out of scope?

5. User Stories / Personas

   • Who are the users? List 3 prioritized user stories.

6. Requirements & Acceptance Criteria

   • Functional requirements (bulleted)
   • Acceptance criteria (given/when/then)

7. Constraints & Assumptions

   • Technical, legal, timeline, team constraints; key assumptions

8. UX / Edge Cases

   • Important UX notes and critical edge cases to validate

9. Rollout & Monitoring

   • Rollout strategy, feature flags, metrics to monitor post-rollout

10. Risks & Mitigation

• Top 3 risks and proposed mitigations

11. Relevant Files / References

• Links to designs, API contracts, DB migrations, or related PRs

12. Checklist

• Spec written, tasks generated, tests defined, docs updated, release notes