create-rfc

Generates structured RFC documents with decision criteria, options comparison, and RACI stakeholder roles.

Updated Sep 15, 2026
One-click install
npx skills add https://github.com/Peterson-Benhame/agent-skills --skill create-rfc-peterson-benhame
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: create-rfc
Source: https://github.com/Peterson-Benhame/agent-skills/tree/main/packages/skills-catalog/skills/%28creation%29/create-rfc
Command: npx skills add https://github.com/Peterson-Benhame/agent-skills --skill create-rfc-peterson-benhame

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Proposing significant technical, process, or vendor decisions without a structured format leads to stalled approvals, hidden assumptions, and stakeholder misalignment. This Skill produces complete Request for Comments documents that drive decisions to closure. ## Core Features & Use Cases - Structured RFC Generation: Creates documents with mandatory sections including Background, Assumptions with confidence levels, weighted Decision Criteria, Options Considered, Action Items, and Outcome. - Decision Discipline: Enforces criteria before options, includes a "Do Nothing" option, and applies a RACI model (Driver, Approver, Contributors, Informed) to clarify ownership. - Adaptive Workflow: Detects RFC type (architecture, process, product, vendor selection, policy), asks targeted questions when context is missing, and writes in the user's language (English, Portuguese, Spanish). - Use Case: Ask the agent to write an RFC comparing self-hosted Kafka, Amazon MSK, and Confluent Cloud, and receive a document with a comparison matrix, cost estimates, and named approvers ready for stakeholder review. ## Quick Start Ask the agent to write an RFC for your proposed change, including the decision deadline, approvers, and any options you already have in mind.

Frequently Asked Questions about create-rfc

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

FAQPage Schema
How do I write an RFC for a technical decision?

Provide the topic, impact level, approvers, and any options you are considering, and the agent generates a complete RFC with background, assumptions, decision criteria, options comparison, and action items. If context is missing, it asks targeted questions first.

What is the difference between an RFC and a TDD?

An RFC decides whether and which option to pursue, targeting broad stakeholders and leadership. A TDD documents how to implement an already-approved decision, targeting the engineering team. RFCs typically come first, with a TDD created after approval.

Can I generate an RFC in Portuguese or Spanish?

Yes, the skill detects the language of your request automatically and generates all section headers and content in that language. Technical terms like API, RFC, and stakeholder remain in English where appropriate.

What sections must a good RFC document include?

Mandatory sections are Header and Metadata, Background, Assumptions, Decision Criteria, Options Considered with at least two options, Action Items, and Outcome. Recommended additions include Relevant Data, Pros and Cons, Cost Estimates, and Resources.

When should I not use an RFC for a decision?

Skip an RFC for bug fixes, minor code changes, single-team low-impact decisions, and implementation of already-approved work. Use a TDD for implementation planning and separate write-ups for exploratory spikes.