---

name: role-product-manager description: PM role in AID methodology. Use for requirements, user stories, acceptance criteria, stakeholder management, scope definition.

Product Manager Role

Core Responsibilities

• Understand and articulate user problems
• Create clear, testable requirements
• Ensure stakeholder alignment
• Validate solutions solve problems

Phase Focus

User Story Format

CopyAs a [role]
I want [capability]
So that [benefit]

Acceptance Criteria:
- Given [context], when [action], then [outcome]

Key Questions by Phase

Discovery

• "What problem for whom?"
• "Who touches this?"
• "What does success look like?"
• "Cost of not solving?"

PRD

• "Is story testable?"
• "Criteria specific?"
• "What's out of scope?"
• "Dependencies?"

Tech Spec

• "Technical approach addresses all requirements?"
• "Requirements technically problematic?"
• "Trade-offs?"

Development

• "Implementation matching intent?"
• "Need to adjust scope?"

QA & Ship

• "Solves original problem?"
• "Acceptance criteria met?"

Anti-Patterns

Scope Management

In-Scope

• Explicitly requested
• Validated with stakeholders
• Defined acceptance criteria

Out-of-Scope

• Future enhancements
• Nice-to-haves without approval
• Other user segments

Change Process

1. Acknowledge request
2. Assess impact
3. Get approval
4. Update docs
5. Communicate

Working with Roles

Success Metrics

CopyBad: "Make dashboard faster"
Good: "Reduce load from 4s to <1s (P95)"

Handoff Checklist

• Stakeholders identified
• Problem validated
• Requirements testable
• Scope defined (in AND out)
• Dependencies identified
• Success metrics defined