rfc-generator

Generate RFC documents with standardized sections for proposals and reviews.

Updated Jan 21, 2026
One-click install
npx skills add https://github.com/vecear/Nipponverb --skill rfc-generator-vecear
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: rfc-generator
Source: https://github.com/vecear/Nipponverb/tree/main/.claude/skills/rfc-generator
Command: npx skills add https://github.com/vecear/Nipponverb --skill rfc-generator-vecear

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Draft comprehensive RFC documents that standardize problem statements, solutions, alternatives, risks, and rollout plans to streamline architecture decisions.

Core Features & Use Cases

  • Generates RFC templates with sections for Problem Statement, Proposed Solution, Alternatives, Risks, and Rollout Plan
  • Supports architecture reviews and design discussions requiring formal proposals
  • Produces review-ready content with templates and examples

Quick Start

Create a complete RFC draft by specifying the problem, proposed solution, alternatives, risks, and rollout plan for a given feature.

Frequently Asked Questions about rfc-generator

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

FAQPage Schema
How do I draft an RFC document for an architecture review?▼

Draft an RFC document by standardizing problem statements, proposed solutions, alternatives, risks, and rollout plans into a complete, review-ready structure for architecture reviews and design discussions.

What is an RFC template used for in software engineering?▼

An RFC template standardizes technical proposals by structuring problem statements, solutions, alternatives, risks, and rollout plans to streamline formal architecture decisions and design discussions.

How do I write a technical proposal that includes risks and alternatives?▼

Write a technical proposal by generating a complete RFC structure with dedicated sections for proposed solutions, alternatives, risks, and rollout plans to ensure comprehensive design documentation.

Can I generate a rollout plan and problem statement for a feature design?▼

Yes, you can generate a rollout plan and problem statement by specifying the feature details to produce a complete RFC draft containing all standard technical proposal sections.

What is the best way to structure technical documentation for design discussions?▼

The best way to structure technical documentation is applying a standardized RFC format that separates problem statements, solutions, alternatives, risks, and rollout plans into review-ready sections.

When do I need formal RFC documentation instead of informal design notes?▼

You need formal RFC documentation when conducting architecture reviews or design discussions that require standardized proposals capturing problems, alternatives, risks, and rollout plans for formal review.