# Product and RFC drafts

Choose a concise product brief for exploration or an RFC for a technical decision.
Start with the problem, the evidence and the decision needed. Develop the useful
parts of the conversation: behavior, constraints, alternatives, tradeoffs, proposed
interfaces, risks, and a testable next step. Skip sections the source cannot support.

Cite exact transcript passages for commitments and constraints. Put inferred
requirements and recommendations under a clear draft label; leave missing owners,
acceptance criteria and approval decisions open. Rejected options are useful only
when their rejection is actually supported. A brainstorming possibility is not
an agreed roadmap. Deliver a compact first draft directly, not a template to fill.