create-rfc

Create formal RFC documents with standardized sections and review periods.

6|Updated Feb 19, 2026
One-click install
npx skills add https://github.com/GeneralJerel/chalk-skills --skill create-rfc
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: create-rfc
Source: https://github.com/GeneralJerel/chalk-skills/tree/main/skills/create-rfc
Command: npx skills add https://github.com/GeneralJerel/chalk-skills --skill create-rfc

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

RFCs are essential for coordinating significant technical changes across teams, but creating a clear, consistent document from scratch is time-consuming. This skill automates the generation of formal RFCs with standardized sections and a defined workflow to improve clarity, traceability, and cross-team alignment.

Core Features & Use Cases

  • Generates a complete RFC document with a numbered title, status, review period, and required reviewers
  • Provides sections like Motivation, Problem Statement, Design Decisions, API Changes, Migration Strategy, and Risks
  • Enforces a standardized format and a defined review timeline to accelerate cross-team feedback

Quick Start

Draft a complete RFC file for an engineering proposal by providing the proposal title or problem statement.

Frequently Asked Questions about create-rfc

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

FAQPage Schema
How do I create a structured RFC for cross-team engineering review?

To create a structured RFC for cross-team engineering review, provide your proposal title or problem statement to generate a formal document with standardized sections including motivation, design decisions, migration strategy, and defined review periods.

What sections are required in a formal technical design proposal?

A formal technical design proposal requires sections for summary, motivation, problem statement, design decisions, API changes, migration strategy, risks, and a defined review timeline to ensure complete cross-team alignment and traceability.

When do I need an RFC document for infrastructure changes?

You need an RFC document for infrastructure changes when your technical proposal affects multiple teams or core infrastructure, requiring formal cross-team input, scoping, alternative analysis, and a structured reviewer plan.

How do I start drafting an engineering RFC from a problem statement?

To start drafting an engineering RFC from a problem statement, input your core problem to automatically generate a complete file with a numbered title, status, required reviewers, and standardized sections saved under the designated engineering docs directory.

What is the best way to standardize the engineering review process for design proposals?

The best way to standardize the engineering review process for design proposals is enforcing a consistent RFC format with defined review periods, required reviewers, and structured migration strategies, ensuring clear traceability and accelerated cross-team feedback.

Does generating an RFC document require external dependencies or specific components?

Generating an RFC document requires no external dependencies or specific components, operating independently to output standardized engineering documentation files directly within your local project structure.