To PRD

Turn the material into a product contract: what improves for whom, and what counts as success.

1. Read the discussion, documents, research, and product context. Separate facts and decisions from proposals and unknowns. Resolve contradictions with the user when they change product direction; otherwise mark them.
2. Identify the target users, current problem, desired outcome, and evidence. If a baseline or target is absent, name the measure and leave its value open.
3. Write the problem and evidence; users and use cases; goals and success measures; in-scope and out-of-scope behavior; main user journey; numbered, observable requirements; constraints; and open decisions. Include failure and accessibility behavior where it affects users.
4. Check that every requirement supports an outcome, each important journey has success and failure paths, and scope excludes future ideas. Mark the source behind consequential claims.

Deliver a usable PRD in the requested location or response. Include implementation choices only if already fixed. Do not create tracker items.

Record this output in docs/plans/ per the doc system, delegating the write to a subagent.