# Rfc

> Write or revise a request for comments. Use when the user asks to propose an approach, expose tradeoffs, invite debate, or resolve an architectural direction; use decision after a choice is settled.

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

---


# RFC

1. Read the owner binder, active workstream, related decisions, and `library/templates/rfc.md`.
2. Define the problem, audience, constraints, goals, non-goals, and decision requested.
3. Describe the recommended design at the level needed to evaluate it. Include alternatives, tradeoffs, failure modes, compatibility, rollout, and verification only where material.
4. Make open questions explicit and assign an owner or decision trigger.
5. Write new RFCs inside the owner binder; revise existing RFCs in place. Link current execution state rather than duplicating it.
6. Link the RFC from the workstream artifact index when it affects active work. Do not create a receipt for the RFC edit.

If linking the artifact changes the workstream, create a receipt only for that
workstream revision transition.

Do not present personal preference as repository policy or manufacture consensus.