irwebtools product-discovery
When to use
Use when the task matches: product-discovery, idea, problem framing.
Purpose
Turn vague requests into a shared problem statement Product roles can verify.
Inputs
- Plain-language idea or request
- Known users and constraints
Process
- Restate the request as a customer/user problem.
- Identify who is affected and in which context.
- Capture the business goal and observable success measures.
- List unknowns; stop for Product answers when material.
- Do not design screens or write code in this skill.
Outputs
- Problem statement
- Users in scope
- Business goal
- Success metrics
- Open questions
Verification
- Confirm each output exists and is reviewable.
- Keep Product validation and engineering verification distinct.
- Do not claim completion without evidence.
Restrictions
- Do not invent business rules to fill gaps.
- Do not jump to React/FSD implementation.
- Do not load delivery skills during discovery.