Combine artefacts when the risk changes
Early in the work, a short brief and rough prototype may be enough to test whether the team is solving the right problem. Once the direction is credible, the PRD can hold the evidence, scope and decisions. Detailed specification should concentrate on the behaviour that would otherwise be invented during design, development or QA.
Use a prototype first when the interaction is the uncertainty
If the team needs to compare journeys, explain a new workflow or observe how somebody responds, make the experience concrete before documenting every rule. Record what the prototype is testing and which parts remain illustrative rather than agreed.
Use a PRD first when alignment is the uncertainty
If people disagree about the problem, intended outcome, audience or first useful slice, a polished interface is premature. Establish the evidence, choices, non-goals and decision owner before moving into detailed interaction or implementation work.
Use a detailed specification first when behaviour carries the risk
Regulated, data-heavy and permission-sensitive products often fail in the conditions around the main journey. Make calculations, decision rules, exceptions, evidence and acceptance conditions explicit, then use a prototype where the team still needs to test presentation or flow.
The handover may need all three
The final set should feel like one source of truth rather than three competing versions. Link each visual state to the relevant decision or rule, keep assumptions labelled, and remove detail that no longer affects the next commitment. The goal is not a larger pack. It is a handover that another team can act on without inventing essential product logic.