Skip to main content
Use an RFC when a proposal needs broad discussion before adoption. Write the proposed direction clearly enough that reviewers can disagree with a specific claim, alternative, or consequence.

Example open question

A useful open question names the consequences of each answer. “Thoughts?” does not give reviewers enough structure.

Review prompts

  • Is the motivation supported by current evidence?
  • Can a reviewer identify what changes for users, operators, data, and callers?
  • Are alternatives described as real choices rather than straw figures?
  • Which accepted choices need separate ADRs or a maintained specification?
Use ADR vs RFC vs technical specification to choose the right record. When the proposal becomes implementable, derive an AI coding plan instead of turning the RFC into a task log. The Rust RFC repository is a primary-source example of a software project using versioned proposals, public discussion, and an accepted or rejected record. This Plannotator template is original and does not reproduce the Rust template. Reviewed July 18, 2026. Written and maintained by the Plannotator documentation team.
Last modified on July 19, 2026