rfc

Author structured RFCs documenting architectural decisions with frontmatter and alternatives.

Updated Feb 4, 2026
One-click install
npx skills add https://github.com/deichworx/smart-swap --skill rfc
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: rfc
Source: https://github.com/deichworx/smart-swap/tree/main/skills/rfc
Command: npx skills add https://github.com/deichworx/smart-swap --skill rfc

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

RFCs are essential for documenting significant architectural decisions, but teams often struggle with consistency, traceability, and shared understanding. This skill provides a structured approach to writing high-quality RFCs that capture problem context, proposed changes, trade-offs, and implementation plans.

Core Features & Use Cases

  • Structured RFC workflow: defines sections for context, decision, consequences, and alternatives.
  • Terminology & Boundaries: promotes ubiquitous language and bounded context to ensure alignment across teams.
  • Use Case: when a team proposes a major system change (e.g., new service, data model, or deployment approach), use this skill to create a complete RFC package.

Quick Start

Write an RFC for a significant architectural change, including problem statement, proposed solution, alternatives, and rollout plan.

Frequently Asked Questions about rfc

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

FAQPage Schema
How do I write an RFC for a major architectural change?▼

Writing an RFC for a major architectural change requires a structured template with problem context, proposed solution, alternatives, and consequences sections to document system design proposals and maintain traceability.

What is domain-driven design guidance for RFC documentation?▼

Domain-driven design guidance for RFCs promotes ubiquitous language and bounded contexts within your documentation to ensure alignment and shared understanding across software engineering teams during system design.

How do I structure an Architecture Decision Record or design doc?▼

To structure an Architecture Decision Record or design doc, apply a structured frontmatter and a templated RFC body that captures problem context, decision records, trade-offs, and implementation rollout plans.

When do I need to create an RFC for system design proposals?▼

You need to create an RFC for system design proposals when a team proposes a major system change, such as introducing a new service, modifying a data model, or shifting a deployment approach.

What should be included in the alternatives and consequences section of an RFC?▼

The alternatives and consequences section of an RFC should document the rejected alternatives and the resulting trade-offs to satisfy traceability and reversibility requirements for architectural decisions.