rfc-specification

An RFC (Request for Comments) is a structured technical document that presents design decisions with evidence-based reasoning. This Skill automates RFC writing by applying a standardized template covering Problem Statement, Goals, Evaluation Criteria, Options Analysis, and Recommendation, ensuring neutral language and explicit trade-off documentation throughout.

A complete RFC includes Header Metadata, Overview, Background & Context, Problem Statement, Goals & Non-Goals, Evaluation Criteria, Options Analysis, Recommendation, Technical Design, Implementation Plan, Open Questions, and Decision Record. This structure separates facts from assumptions and enforces evidence-based evaluation at each stage.

Use an Evaluation Criteria Framework with standard technical, operational, and business categories rated against weighted scoring templates. Document each option's trade-offs systematically, supported by evidence, then present a recommendation with clear rationale—separating neutral analysis from subjective preference.

Use RFCs for critical technical decisions, system redesigns, and cross-team architecture reviews where alignment and documented rationale matter. RFCs provide lifecycle tracking (DRAFT, REVIEW, APPROVED, COMPLETED, SUPERSEDED) and create an auditable record of decision-making that informal docs cannot match.

Yes. RFCs excel at evaluating technology options by structuring each candidate's pros, cons, and constraints against weighted criteria. The template forces explicit trade-off analysis, preventing overlooked risks and ensuring stakeholders understand why one selection won over alternatives.

The RFC structure enforces this separation by requiring explicit Background & Context, measurable Evaluation Criteria, and evidence-sourced Options Analysis. This discipline prevents assumptions from masquerading as facts and makes hidden dependencies visible to reviewers and decision-makers.