product-definition
When to use
Use when the task matches: product-definition, feature brief, scope.
Purpose
Produce a feature brief Product and Development can execute without guessing intent.
Inputs
- Discovery outputs
- Known business rules and constraints
Process
- Write a feature brief in Product language.
- Capture business rules and explicit exclusions.
- Point to user-story and acceptance-criteria skills for detail.
- Confirm scope boundary before UX or coding.
Outputs
- Feature brief
- Scope boundary
- Business rules summary
- Links to stories and acceptance
Verification
- Confirm each output exists and is reviewable.
- Keep Product validation and engineering verification distinct.
- Do not claim completion without evidence.
Restrictions
- Do not expand scope without Product confirmation.
- Do not replace UX journey work.
- Do not invent compliance or legal rules.