Condense the supplied requirements into a brief for discussing or implementing the stated need. Use this for required behavior and scope, not a solution design or a new specification.

Start with the user and the task or problem. Group requirements by behavior. Retain actors, permissions, inputs, outputs, limits, timing, dependencies, and failure behavior. Preserve requirement identifiers when supplied. Keep must-have behavior distinct from preferences and future ideas. Do not replace a user need with the first suggested implementation.

Separate in-scope requirements, explicit exclusions, and unresolved questions. Preserve numerical boundaries and whether they are inclusive. Do not resolve conflicting statements silently; show the conflict beside the affected requirement.

Use a short goal followed by labeled bullets. Remove historical discussion and repeated rationale unless they explain a constraint. Keep an open question open, and do not add acceptance tests, architecture, features, or priorities that the source does not support.