Create RFC

Overview

Create a structured Request for Comments (RFC) document for significant technical proposals that require cross-team review and consensus. RFCs are heavier than ADRs -- they are appropriate when a proposal affects multiple teams, introduces new infrastructure, changes a core abstraction, or has a blast radius that demands structured feedback before commitment.

Workflow

1. Read project context -- Read .chalk/docs/engineering/ for existing architecture docs, ADRs, and prior RFCs. Understand the current system state so the proposal builds on established decisions rather than contradicting them.

2. Determine the next RFC number -- List files in .chalk/docs/engineering/ matching the pattern *_rfc_*.md. Find the highest number and increment by 1. If no RFCs exist, start at 1.

3. Clarify the proposal scope -- From $ARGUMENTS and conversation context, identify:

   • The specific technical change being proposed
   • The problem or opportunity motivating it (why now, not six months ago or six months from now)
   • The teams and systems affected
   • Whether this is the right size for an RFC (if it is a single-team decision with limited blast radius, suggest an ADR instead)
   • Ask the user for clarification if the scope is ambiguous or too broad