new-rfc

Draft answer-first RFCs for proposed repository changes.

15|5|Updated May 4, 2026
One-click install
npx skills add https://github.com/eugenelim/agent-ready-repo --skill new-rfc-eugenelim
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: new-rfc
Source: https://github.com/eugenelim/agent-ready-repo/tree/main/.agents/skills/new-rfc
Command: npx skills add https://github.com/eugenelim/agent-ready-repo --skill new-rfc-eugenelim

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and assets (resource) components.

What problem does it solve?

This Skill helps you turn a proposed change into a clear, research-backed RFC that gives reviewers a decision to make instead of a vague discussion to rescue.

Core Features & Use Cases

  • Answer-first drafting: Leads with the ask, the recommended decision, and the reason it should be approved.
  • Research and de-risking: Separates the proposal into subpoints, checks repository precedent, looks for external prior art, and tests the riskiest assumption.
  • Review-ready structure: Organizes the RFC into problem and goals, options considered, risks, evidence, open questions, and follow-on artifacts.
  • Use case: A team wants to change a cross-cutting convention, replace an architecture choice, or open discussion on a major process change before implementation begins.

Quick Start

Use the new-rfc skill to draft a repository RFC for a proposed change, starting with the ask and then filling in research, options, risks, evidence, and open questions.

Frequently Asked Questions about new-rfc

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I write an RFC for a proposed architecture change in my repository?▼

Draft an RFC for an architecture change by leading with the recommended decision and request, then separating the proposal into research-backed options, repository precedent, and risk analysis before a self-review gate. This structure gives reviewers a clear decision to make.

What is the best way to structure an RFC for a cross-cutting design decision?▼

Structure an RFC for cross-cutting design decisions using an answer-first format that organizes problem and goals, options considered, risks, evidence, and open questions. This review-ready organization replaces vague discussions with explicit decision framing.

When do I need an RFC instead of just implementing a convention change directly?▼

You need an RFC when proposed changes involve cross-cutting convention changes, reversals of prior decisions, or major process changes where discussion must happen before implementation begins. It forces explicit decision framing and risk analysis.

How do I research prior art and de-risk assumptions when drafting a technical proposal?▼

Research prior art and de-risk assumptions by checking repository precedent, looking for external prior art, and testing the riskiest assumption within your proposal. This research-backed approach requires verifiable citations and explicit non-goals to bound the scope.

Can I use this RFC drafting process for convention reversals of prior decisions?▼

Yes, you can use this RFC drafting process for convention reversals of prior decisions. It applies structured decision framing, research-backed options, and a mandatory self-review gate before handoff to ensure the reversal is rigorously justified.

What should I include in the review-ready structure of a research-backed RFC?▼

Include the ask, the recommended decision, problem and goals, options considered, risk analysis, verifiable evidence, open questions, and follow-on artifacts. This review-ready structure ensures reviewers have everything needed to approve or reject the proposal.