create-rfc

Generate RFC documents with required decision fields and structured sections.

Updated Mar 29, 2026

Search Tags:#architecture #governance #stakeholder #process #rfc #proposal #decision-making

Ready to run

npx skills add https://github.com/oiagorodrigues/qcontabil --skill create-rfc-oiagorodrigues

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: create-rfc
Source: https://github.com/oiagorodrigues/qcontabil/tree/main/.cursor/skills/create-rfc
Command: npx skills add https://github.com/oiagorodrigues/qcontabil --skill create-rfc-oiagorodrigues

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Proposals for significant changes often suffer from unclear scope, missing stakeholders, and weak decision records. This skill generates clear RFC documents that capture options, criteria, and a formal decision path to align teams and drive accountable progress.

Core Features & Use Cases

Interactive workflow that collects required fields (Driver, Approver, Assumptions with confidence, Decision Criteria) and produces a complete RFC draft.
Enforces mandatory sections (Background, Assumptions, Decision Criteria, Options Considered, Action Items, Outcome) and includes a "Do Nothing" option to ensure honest evaluation.
Supports multiple RFC types (Technical/Architecture, Process/Workflow, Product/Feature, Vendor/Tool Selection, Policy/Compliance) and automatically adapts the RFC language to the user's preferred language.

Quick Start

Write an RFC for migrating our database from MySQL to PostgreSQL.

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 software architecture proposal?▼

To write an RFC for software architecture, you need to define the Driver, Approver, Assumptions, and Decision Criteria. This process generates a structured document with mandatory sections like Background, Options Considered, and an auditable Outcome to ensure traceable decisions.

What is the best way to document technical decisions and align stakeholders?▼

Documenting technical decisions to align stakeholders requires capturing options, criteria, and a formal decision path in an RFC. This approach enforces mandatory sections and includes a "Do Nothing" option to ensure honest evaluation and accountable progress across teams.

Can I create RFCs for process workflow changes and vendor selection?▼

Yes, you can create RFCs for process workflow changes and vendor selection. The RFC process supports multiple proposal types including Technical/Architecture, Process/Workflow, Product/Feature, Vendor/Tool Selection, and Policy/Compliance, adapting language to your preferred context.

How do I structure a proposal to include assumptions and decision criteria?▼

Structure a proposal by enforcing mandatory sections: Background, Assumptions with confidence levels, Decision Criteria, Options Considered, Action Items, and Outcome. This interactive workflow collects required fields to produce a complete and rigorous RFC draft.

Does generating an RFC require defining a formal decision outcome?▼

Yes, generating an RFC requires defining a formal decision outcome. The process mandates an auditable Outcome section alongside explicit Driver and Approver roles to guarantee traceable decisions and align teams on significant changes.

What sections are mandatory when drafting an RFC?▼

Mandatory sections when drafting an RFC include Background, Assumptions, Decision Criteria, Options Considered, Action Items, and Outcome. The structure also enforces evaluating a "Do Nothing" option to ensure honest assessment of the proposed change.