Requirements From Brief

Use this skill to translate product intent into requirements before interface solutions are chosen. Requirements describe what the user and system need, not which component to use.

Process

1. Extract user goals, business goals, constraints, and data/API/auth dependencies.
2. Write functional requirements as FR-XX: The system shall [action] when [condition] so that [outcome].
3. Write non-functional requirements for performance, accessibility, responsiveness, browser support, security/privacy, reliability, and internationalization when relevant.
4. Identify explicit out-of-scope items for v1.
5. Identify assumptions and open questions.
6. Recommend acceptance criteria, sitemap, or user-flow mapping as the next step.

Output format

## Requirements