# Create Rfc

> Creates structured Request for Comments (RFC) documents that propose a change, compare alternatives against explicit decision criteria, and drive aligned decisions across teams. TRIGGER when: the user asks to create or write an RFC, draft a proposal, compare options, align stakeholders, get approval for a significant change, or propose a technical/process/product/vendor/policy change before deciding. SKIP for: decisions that have already been made (use `/create-adr` to record them), implementation planning or breaking work into tasks (use `/forge plan`), or informal one-off asks that don't need stakeholder alignment.

- Skill: `emiliosheinz/create-rfc` (Agent Skill, multi-file: 7 files)
- Install (CLI): `npx skillmds@latest add emiliosheinz/create-rfc`
- Raw SKILL.md: https://api.skillmd.com/api/skills/emiliosheinz/create-rfc/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Product & Planning
- Author: emiliosheinz (https://skillmd.com/u/emiliosheinz)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/emiliosheinz/create-rfc

---


# Create RFC

Produce one RFC per invocation. An RFC proposes a decision that has *not*
yet been made and drives stakeholder alignment; if the decision is already
made, use `/create-adr` to record it. Follow the five-step process — do not
skip Step 2 (validate mandatory fields) or draft before every mandatory
field is present.

## Hard rules

- **Never invent facts.** If a mandatory field is missing, ask. Never fill
  Background, Assumptions, or Options with plausible-sounding filler.
- **Never present a foregone conclusion.** If only one option is real, the
  document is an ADR, not an RFC — use `/create-adr` instead.
- **Decision criteria come before options.** Criteria written after options
  look like justification for a preferred choice.
- **Include "do nothing" as an explicit option** for any significant change.
- **Never skip trade-offs.** Every option needs honest cons alongside pros.
- **Never write in a language other than the user's.** Match the language
  the user is using in this session.

## Dispatch

Run the process in order. **Read the matching reference file fully before
acting** — it is the playbook for that step.

| Step | Read | Purpose |
|------|------|---------|
| 1 — Gather context | `references/process.md` | Ask for topic, impact, urgency, options in mind |
| 2 — Validate mandatory fields | `references/process.md` | Ensure title, background, RACI, criteria, options, recommendation are present |
| 3 — Tailor to RFC type | `references/types.md` | Technical / Process / Product / Vendor / Policy — extra focus areas |
| 4 — Generate | `templates/rfc.md` + `references/numbering.md` | Fill template, assign number, run quality checklist |
| 5 — Place + next steps | `references/process.md` | Confirm file location, print summary + follow-ups |

Run the quality checklist (`references/quality.md`) before finalizing —
honest options, weighted criteria, quantified background, explicit
assumptions.

## Template

Pure markdown scaffold. Load only when writing:

- `templates/rfc.md` — mandatory + recommended sections. Delete any
  recommended section that would be empty; keep every mandatory section
  even if the value is `*to be confirmed*`.

## Universal rules

1. **Honesty.** Options are compared honestly against the criteria; pros
   and cons are real; assumptions are surfaced with confidence levels and
   invalidation triggers.
2. **"Do nothing" is always an option** for significant changes — it forces
   honest evaluation of whether change is worth the cost.
3. **Outcome is a placeholder** during drafting — fill it after the
   decision is made, then link to the resulting ADR if the decision is
   worth preserving.
4. **RFCs are for decisions, not implementation.** Once decided, hand off
   to `/create-adr` (record) and `/forge` (build).
5. **Date everything** and record the impact level up front.
6. **Language adaptation.** Always write the RFC in the user's language.
7. **Confirm before writing.** Suggest the file path in Step 5; write only
   after the user confirms placement.

## Sibling skills

Reach for these at any point in the flow:

- **`/create-adr`** — the decision *has* been made. Use ADR to record the
  what/why/consequences as an immutable historical record. RFC → decision →
  ADR is the natural flow for significant choices.
- **`/forge`** — spec-driven implementation. Once the RFC is decided, use
  `/forge specify | design | plan | execute` to break the chosen option
  into shippable work.

## Attribution

Based on [create-rfc](https://github.com/tech-leads-club/agent-skills/blob/main/packages/skills-catalog/skills/(creation)/create-rfc/SKILL.md)
by [Tech Leads Club](https://github.com/tech-leads-club), licensed under
[CC-BY-4.0](https://creativecommons.org/licenses/by/4.0/). Changes have been
made to the original.