rfc

Generates a structured RFC document with problem, goals, alternatives, risks, and rollout plans.

Updated Apr 9, 2026
One-click install
npx skills add https://github.com/nist0/CoDev --skill rfc-nist0
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: rfc
Source: https://github.com/nist0/CoDev/tree/main/.github/skills/rfc
Command: npx skills add https://github.com/nist0/CoDev --skill rfc-nist0

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

Crafting a comprehensive Request for Comments (RFC) for team proposals can be time-consuming and complex. This Skill simplifies the process with a structured template that ensures all necessary elements are included.

Core Features & Use Cases

  • Structured Template: Ensures a comprehensive RFC document with all essential sections.
  • Automated Outline: Provides a copy/paste-ready document outline for quick drafting.
  • Workflow Guide: Offers step-by-step instructions and a self-check list for quality assurance.
  • Use Case: Use this Skill to create an RFC for an API change, where you need a clear proposal with a risk assessment and implementation plan.

Quick Start

Create an RFC proposal for a new API endpoint 'get-products' by using the rfc skill.

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 document for a software design proposal?

To write an RFC document for a software design proposal, use a structured template that automates outline generation and ensures all essential sections like problem statement, goals, alternatives, risks, and rollout plans are included.

What sections should be included in a structured RFC for API changes?

A structured RFC for API changes must include a problem statement, goals, alternatives, risks, and rollout plans. The document ensures comprehensive team collaboration by providing a copy/paste-ready outline for quick drafting.

How do I create a copy paste ready RFC outline for team collaboration?

You create a copy/paste-ready RFC outline for team collaboration by automating the document structure, which instantly provides all required sections and a workflow guide with a self-check list for quality assurance.

Can I use a structured RFC template for evaluating technical risks and alternatives?

Yes, you can use a structured RFC template for evaluating technical risks and alternatives. The template specifically enforces the inclusion of dedicated sections for risk assessment and alternative considerations before rollout.

Does generating an RFC document require any external dependencies?

Generating an RFC document with this approach requires no external dependencies. The template operates independently with built-in scripts and references to provide a complete workflow guide and self-check list.

What is the best way to ensure quality when proposing design changes?

The best way to ensure quality when proposing design changes is to follow a structured workflow guide with a self-check list. This guarantees all required sections are included and validated before team review.