skills.rest
zinohome
zinohomeCOMMUNITY
Explore all skills by this author →
GitHub

rfc-generator

Generates Request for Comments documents for technical proposals and architecture decisions.

Updated Mar 16, 2026
Search Tags:#architecture#documentation#rfc#generate#design doc#review process#technical proposal
One-click install
npx skills add https://github.com/zinohome/RTMessage --skill rfc-generator-zinohome
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: rfc-generator
Source: https://github.com/zinohome/RTMessage/tree/main/.github/skills/rfc-generator
Command: npx skills add https://github.com/zinohome/RTMessage --skill rfc-generator-zinohome

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Writing structured technical proposals is time-consuming and inconsistent across teams. This Skill produces complete RFC documents covering problem statements, solution design, alternatives, risks, and rollout plans so reviewers get all the context they need. ## Core Features & Use Cases - Full RFC Template: Generates documents with summary, problem statement, proposed solution, detailed design, alternatives, tradeoffs, risks, rollout plan, success metrics, cost analysis, and timeline. - Structured Review Process: Guides the draft, review, approval, and implementation lifecycle with defined phases and checklists. - Use Case: An engineer proposing PostgreSQL read replicas can generate a complete RFC including architecture diagrams, routing code samples, cost tables, and a phased six-week rollout plan ready for architecture review. ## Quick Start Generate an RFC for adding read replicas to our PostgreSQL database including problem statement, alternatives, risks, and rollout plan.

Frequently Asked Questions about rfc-generator

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

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

Start with a clear problem statement and success criteria, then describe the proposed solution with architecture details. Include at least two alternatives with verdicts, tradeoffs, risks with mitigations, a phased rollout plan, and measurable success metrics.

What sections should a design doc or RFC include?▼

A complete RFC includes summary, problem statement, proposed solution, detailed design, alternatives considered, tradeoffs, risks and mitigations, rollout plan, success metrics, cost analysis, timeline, and open questions for reviewers.

How long should the RFC review process take?▼

A typical process runs about four weeks: one week for drafting, one to two weeks for review and iteration, and one week for approval. Implementation tracking continues afterward with the RFC updated as learnings emerge.

When should I write an RFC instead of just building the feature?▼

Write an RFC when changes affect shared infrastructure, introduce architectural tradeoffs, require cross-team coordination, or carry significant cost or risk. Small isolated changes typically do not need formal review.

How many alternatives should an RFC consider?▼

Document at least two alternatives with pros, cons, and a clear verdict for each. This demonstrates the design space was explored and helps reviewers understand why the proposed approach was selected.

Related Skills

Explore More Software Engineering Skills→
Agile-VAgile-V
50

observability-planner

Plan and implement production observability with metrics, alerts, dashboards, and SLOs.

Official
Advanced
Andamio-PlatformAndamio-Platform

product-iteration

Orchestrate product feedback loops across test, design, triage, and ship phases.

Official
Advanced
malinskibeniaminmalinskibeniamin
3

steelman

Identify user claims, gather repository evidence, and issue a formal verdict.

Community
Advanced
RefoundAIRefoundAI
1.2k

running-effective-meetings

Design structured meeting agendas with clear objectives and action items.

Official
Intermediate