The Build course covers three framework boxes, and Pragmatic Institute names them directly. Requirements, Use Scenarios and Stakeholder Communications. The first two are the handover from market knowledge to the team that will build something.
What a requirement is here
The framework's wording is worth reading twice. A requirement articulates personas and their problems so that the appropriate products can be built. It does not describe a mechanism.
The reason is division of expertise. The product manager knows the market. The development team knows what is cheap, what is expensive and what will break in two years. A requirement that arrives as a specified solution collapses those two into one and discards the half that was better informed about implementation.
A useful requirement carries the persona, the problem in their terms, evidence of how widespread and urgent it is, and what would count as the problem being solved. What it does not carry is the shape of the screen.
Use scenarios
A use scenario is the problem told as a story with the context still attached. Who the person is, what they are trying to accomplish, what is happening around them, what they do today and where it goes wrong.
The context is the point. A requirement stripped to a single sentence loses the facts that decide the design, such as the fact that this happens on a phone in a loading bay, or during a two hour window at month end, or while three other people wait for the result.
The framework calls use scenarios one component of requirements rather than a substitute for them. The requirement states the problem and its prevalence. The scenario makes it concrete enough to design against.
What this gives development
Room to solve it better. A team that understands who has the problem and why it matters will often propose something cheaper and more effective than the solution the product manager had in mind, and can make sensible calls on the hundred small decisions that never make it into any document.
It also gives them something to check against. When a question comes up mid sprint, the scenario answers it more often than the acceptance criteria do.
Prioritising the requirements
The framework wording includes prioritise as well as articulate. Requirements compete for the same capacity, and the ranking is done with the market evidence attached to each one rather than by who asked. That is the subject of prioritising with market data, and the reason requirements are written with their evidence in the first place.