Decompose a Vague Feature Request

A stakeholder has described a feature in high-level terms. Help me break it down into concrete, buildable requirements.

STAKEHOLDER REQUEST:
"[Paste the stakeholder's exact words or meeting notes]"

PRODUCT CONTEXT:
- Product: [App/platform name and type]
- Platform: [iOS (Swift/SwiftUI) / Android (Kotlin/Compose) / Both]
- Target users: [Who will use this feature]
- Related existing features: [What already exists that this connects to]

Please provide:
1. A clear summary of what the stakeholder actually wants (in plain language)
2. A list of assumptions I should validate with the stakeholder
3. Questions I should ask before writing stories
4. A preliminary breakdown into 3-8 user stories
5. Any risks or dependencies I should flag early