write-rfc

Draft structured RFCs with decision rationale and rollout steps.

43|6|Updated Mar 16, 2026

Search Tags:#design #planning #architecture #documentation #rfc

Ready to run

npx skills add https://github.com/1024XEngineer/bytemind --skill write-rfc-1024xengineer

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: write-rfc
Source: https://github.com/1024XEngineer/bytemind/tree/main/internal/skills/write-rfc
Command: npx skills add https://github.com/1024XEngineer/bytemind --skill write-rfc-1024xengineer

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

RFC drafting can be time-consuming and prone to inconsistent formatting. This Skill provides a repeatable structure and guidance to produce reviewable proposals with explicit rationale and rollout plans.

Core Features & Use Cases

Structured sections: Context and Problem, Goals and Non-Goals, Candidate Options, Trade-offs, Proposed Design, Rollout Plan, Verification Plan, Risks and Mitigations.
Enforces explicit assumptions and testable risks, with clear next steps and ownership for each RFC.
Use case: when planning a major architecture change or migration, generate a complete RFC that stakeholders can review and approve.

Quick Start

Draft an RFC by outlining context, goals, options, trade-offs, design, rollout, and verification.

Frequently Asked Questions about write-rfc

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

FAQPage Schema

How do I draft a technical RFC for an architecture migration?▼

Drafting a technical RFC for an architecture migration involves structuring context, goals, candidate options, trade-offs, proposed design, and a rollout plan. The process enforces explicit assumptions, risk tagging, and testable milestones for stakeholder review.

What sections should be included in a software design proposal?▼

A software design proposal should include Context and Problem, Goals and Non-Goals, Candidate Options, Trade-offs, Proposed Design, Rollout Plan, Verification Plan, and Risks and Mitigations. This structure ensures reviewable proposals with explicit decision rationale.

When do I need a formal RFC document for project planning?▼

You need a formal RFC document when planning a major architecture change or migration that requires stakeholder review and approval. It provides a repeatable structure to document explicit rationale, testable risks, and clear next steps with ownership.

How do I document trade-offs and verification plans in technical documentation?▼

Documenting trade-offs and verification plans requires outlining candidate options alongside proposed designs and testable milestones. Explicit assumptions and risk tagging are enforced within the structure to produce clear rollout steps and actionable decisions.

Can I use structured RFC drafting for small scope project changes?▼

Structured RFC drafting supports technical design and RFC drafting across project scopes, including smaller changes. It enforces explicit assumptions, testable risks, and clear next steps regardless of scale to ensure stakeholders can review and approve actionable decisions.