spec-rfc

To create an RFC document for design uncertainty, define problem statements, viable options, decision rationale, verification, and rollback paths. This formalizes constraints and reduces rollout risk by stabilizing contracts prior to coding.

Draft an RFC when your plan shows multiple viable design options, rollback concerns, or cross-module coordination needs. It stabilizes contracts and validates design choices before coding to reduce implementation risk.

An RFC for cross-module coordination should include a problem statement, design options, decision rationale, verification, rollback paths, milestones, and observability guidelines. This structure stabilizes contracts and enables traceable handoffs.

Structure rollback and verification in architecture documentation by defining explicit rollback paths and verification steps within your RFC. This ensures milestones and observability guidelines are established before coding begins.

Writing an RFC helps cross-team coordination by capturing design options, scope, and milestones in auditable records. It provides clear decision rationale and context to guide subsequent implementation and traceable handoffs.

The best way to document design decisions is using an RFC structure that explicitly defines goals, non-goals, context, and decision rationale. This formalizes constraints and produces auditable records for implementation handoffs.