# Rfc Process

> Write, number, and advance RFCs in the house shape used across amkisko libraries. Use when adding an RFC, claiming an id, copying the template, mapping status, flattening an RFC tree, or aligning a repo to this process.

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

---


# RFC process

Read `rfc-process.md` in this skill directory for claim, template, types, statuses, length, and isolation. Read `references/template.md` when copying or replacing `rfcs/0000-template.md`.

## Quick reference

```text
read rfcs/README.md → claim ids/NNNN → copy template → omit empty sections → PR rfc: NNNN title → implementation cites RFC-NNNN
```

Keep existing RFC numbers. Project bands and extra tests stay in that repo's `rfcs/README.md`. Product RFCs specify a design (suggestion, motivation, specification, effects, alternatives, prior art). Version numbers belong in changelogs.