Requirements definition

Use this skill before implementation when the request is ambiguous, product-facing, or user-facing.

Workflow

1. Identify the user, problem, and desired outcome.
2. Separate confirmed facts from assumptions.
3. Define requirements as observable behavior.
4. Write acceptance criteria that QA can verify.
5. List non-goals to prevent scope creep.
6. Flag open questions only when they block implementation.

Output

Return: