Clarify ambiguous requirements through structured questioning and produce detailed, implementation-ready specifications. Acts as PdM to identify unclear points and resolve them via AskUserQuestion. Use PROACTIVELY when user mentions requirements, specs, PRD, refine, detail, clarify requirements, or asks to detail/refine app ideas. Examples: <example>Context: User has rough idea user: 'Help me refine this app spec' assistant: 'I will use refining-requirements skill' <commentary>Triggered by spec refinement request</commentary></example> <example>Context: Planning phase user: 'Let me detail the requirements' assistant: 'I will use refining-requirements skill' <commentary>Triggered by requirements detailing</commentary></example>
Clarify ambiguous requirements through structured questioning and produce detailed, implementation-ready specifications.
Use PROACTIVELY when:
After this skill: Use designing-wireframes for UI/UX visualization, then planning-tickets for GitHub Issues.
Phase 1: Read & Understand
|
Phase 2: Identify Ambiguities
|
Phase 3: Question Rounds (AskUserQuestion)
|
Output: Detailed requirements document
Systematically check for ambiguities in these categories:
| Category | Questions to Consider |
|---|---|
| Layout | Screen structure, section arrangement, navigation |
| Interaction | Tap, swipe, long-press behaviors |
| Feedback | Success/error states, loading indicators |
| Empty States | What to show when no data exists |
| Category | Questions to Consider |
|---|---|
| Navigation | How users move between screens |
| Data Entry | Input methods, validation, defaults |
| Edge Cases | What happens at boundaries (100%+, limits) |
| Error Handling | How to handle and display errors |
| Category | Questions to Consider |
|---|---|
| Limits | Free vs Pro, numeric limits |
| Defaults | Initial values for settings |
| Calculations | Formulas, timing, thresholds |
| Category | Questions to Consider |
|---|---|
| Thumb-Zone Design | Are primary actions in the bottom zone (easy thumb reach)? |
| Touch Targets | Are all interactive elements >= 44x44pt? |
| Loading States | How to show loading (spinner, skeleton, shimmer)? |
| Haptic Feedback | Use vibration feedback for confirmations/warnings? |
| Animation | iOS standard spring animations or custom? Duration/easing? |
| Category | Questions to Consider |
|---|---|
| WCAG Compliance | Target AA or AAA? Contrast ratio 4.5:1? |
| Touch Targets | Minimum 44x44pt for all interactive elements? |
| Screen Reader | accessibilityLabel for all interactive elements? VoiceOver support? |
| Focus Order | Logical tab order? Modal focus trapping? |
| Category | Questions to Consider |
|---|---|
| Delete Actions | Immediate / Undo option / Confirmation dialog? |
| Form Validation | Inline real-time / On submit? Specific validation rules? |
| Error Display | Toast / Alert / Inline error message? Auto-dismiss timing? |
| Retry Logic | Auto-retry with exponential backoff? Manual retry button? |
| Category | Questions to Consider |
|---|---|
| Dark Mode | Light only (MVP) / System automatic / Manual toggle? |
| Empty States | Simple text / Icon + text / CTA button? |
| Color Scheme | Platform standard colors or custom brand colors? |
Use AskUserQuestion tool to clarify ambiguities. Group related questions (max 4 per round).
UI Style Questions:
- Size selection UI format?
-> Bottom Sheet / Modal / Inline Expansion
- Button design?
-> Icon+Text / Icon only / Text only
- List display format?
-> Grouped / Flat
Behavior Questions:
- Display when over 100%?
-> Cap at 100% / Show excess in different color / Ring format
- Delete confirmation?
-> With confirmation / Without confirmation
- Error behavior?
-> Warn and continue / Block
Navigation Questions:
- Screen access method?
-> Tab bar / Header icon / In-screen link
- Onboarding steps?
-> 1 screen / 3 steps / 4 steps
Pro/Free Questions:
- Paywall display timing?
-> On feature tap / At boundary reached
- Paywall UI?
-> SDK standard / Custom
Mobile UX Questions (CRITICAL for mobile apps):
- Primary action button placement?
-> Bottom (Thumb-Zone) fixed / Center / Within content
- Loading display format?
-> Simple spinner / Skeleton Screen / Content Shimmer
- Haptic Feedback?
-> Implement (on success, warning) / Don't implement
Accessibility Questions (MUST ASK):
- Accessibility requirements?
-> WCAG AA compliance / Basic support only / Not in MVP
- VoiceOver/TalkBack support?
-> Full support / Basic (accessibilityLabel) / Not in MVP
Error Prevention Questions:
- Delete operation UX?
-> Immediate (no confirmation) / Toast with Undo / Confirmation dialog
- Define detailed validation rules?
-> Define (specify char count, range, etc.) / Decide at implementation
- Error display format?
-> Toast / Alert / Inline message
Visual Design Questions:
- Dark mode support?
-> Light mode only (MVP) / Auto-follow system / Manual toggle
- Empty State display?
-> Simple text / Icon + text / With CTA
After gathering all answers, update the requirements document with:
Use the requirements-section.md template for consistent formatting.
When this skill is activated:
Suggest using designing-wireframes skill for UI/UX visualization if screens need to be designed.