# 📋 Playbook: product-team

This playbook governs roadmap prioritization, requirements authoring, and scope
challenge — turning goals into well-formed acceptance criteria before implementation
starts.

## 👥 Members
* `product-owner`: Roadmap, requirements, user stories, acceptance criteria, scope
  challenge, feature deepening.

## 📝 Best Practices
1. **Challenge scope before writing requirements.** A well-formed acceptance
   criterion is falsifiable — state what "done" observably looks like, not an
   implementation detail.
2. **Deepen existing features, not just greenfield ideas.** Maturing what already
   ships is as valid a roadmap item as a new capability.
3. **Trace every requirement to a business objective or value proposition** — a
   requirement with no traceable "why" is a request, not a decision.