rfc-writer

Draft structured RFC documents from rough ideas or requirements.

3|Updated Mar 31, 2026
One-click install
npx skills add https://github.com/sunny0826/open-source-skills --skill rfc-writer-sunny0826
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: rfc-writer
Source: https://github.com/sunny0826/open-source-skills/tree/main/skills/rfc-writer
Command: npx skills add https://github.com/sunny0826/open-source-skills --skill rfc-writer-sunny0826

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Converting rough ideas or scattered requirements into a complete, well-structured RFC document is time-consuming and error-prone without a repeatable template.

Core Features & Use Cases

  • Structured RFC generation: automatically fills Background, Problem Statement, Proposed Solution, Alternatives Considered, and Unresolved Questions.
  • Multilingual output: adapts to user prompts in Chinese or English.
  • Guidance and justification: expands missing details with reasoned assumptions and documents trade-offs.

Quick Start

Provide a rough idea or requirements, and ask the assistant to draft an RFC document.

Frequently Asked Questions about rfc-writer

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

FAQPage Schema
How do I draft an RFC document from scattered requirements?

To draft an RFC document from scattered requirements, provide your rough ideas to the assistant, which then generates a structured technical proposal covering Background, Problem Statement, Proposed Solution, Alternatives Considered, and Unresolved Questions. It expands missing details with reasoned assumptions to ensure a complete architecture redesign.

What is the best way to structure a technical proposal for system design?

The best way to structure a technical proposal for system design is to enforce standard RFC sections: Background, Problem Statement, Proposed Solution, Alternatives Considered, and Unresolved Questions. This framework ensures clear, reasoned rationale for chosen architecture approaches and trade-offs.

Can I generate bilingual RFC documentation for architecture redesigns?

Yes, you can generate bilingual RFC documentation for architecture redesigns. The RFC writer adapts to user prompts in either Chinese or English, automatically generating the complete technical proposal and structured documentation in the language of your provided requirements.

How does this approach handle missing details in a rough technical proposal?

Handling missing details in a rough technical proposal involves expanding the scattered requirements with reasoned assumptions. The RFC generation process documents trade-offs and generates clear, reasoned rationale for chosen approaches to fill gaps in your initial system design ideas.

When do I need a formal RFC for my architecture redesign?

You need a formal RFC for your architecture redesign when converting rough ideas into a complete, well-structured technical proposal. It is essential for technical proposals requiring documented trade-offs, clear rationale for chosen approaches, and a record of alternatives considered and unresolved questions.

Does drafting an RFC require a specific template or dependencies?

Drafting an RFC does not require specific dependencies or a manually configured template. The process automatically enforces structured RFC sections directly from your rough idea, generating the Background, Proposed Solution, and other necessary technical proposal components without prerequisite setup.