write-rfc

Generate structured engineering RFCs with standardized sections for motivation, architecture, and tradeoffs.

9|3|Updated Jun 13, 2026
One-click install
npx skills add https://github.com/Sir-chawakorn/sanook-cli --skill write-rfc-sir-chawakorn
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: write-rfc
Source: https://github.com/Sir-chawakorn/sanook-cli/tree/main/skills/write-rfc
Command: npx skills add https://github.com/Sir-chawakorn/sanook-cli --skill write-rfc-sir-chawakorn

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill streamlines the creation of technical proposals and engineering design documents, ensuring that complex changes are thoroughly vetted, documented, and aligned with team standards before implementation.

Core Features & Use Cases

  • Structured Proposal Drafting: Generates comprehensive RFCs covering motivation, design, tradeoffs, and migration plans.
  • Review-Ready Formatting: Enforces best practices like TL;DR summaries, risk assessment tables, and explicit decision-making sections.
  • Use Case: When planning a major system refactor or a new service architecture, use this skill to produce a standardized document that clearly communicates the proposed solution and alternatives to stakeholders for sign-off.

Quick Start

Use the write-rfc skill to draft a new design document for the proposed user authentication service migration.

Frequently Asked Questions about write-rfc

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

FAQPage Schema
How do I draft an engineering RFC for a system migration?

To draft an engineering RFC for a system migration, generate a structured technical proposal covering motivation, architecture, tradeoffs, and migration strategies. This enforces standardized sections to ensure complex changes are risk-aware and ready for stakeholder sign-off.

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

The best way to structure a technical design proposal is to enforce standardized sections including TL;DR summaries, motivation, architecture, and risk assessment tables. This review-ready formatting clearly communicates proposed solutions and alternatives to stakeholders.

When do I need to write a formal technical design doc instead of just coding?

You need to write a formal technical design doc when planning a major system refactor or new service architecture. It ensures complex changes are thoroughly vetted, documented, and aligned with team standards before implementation begins.

How do I document architecture tradeoffs and migration plans in a design doc?

To document architecture tradeoffs and migration plans in a design doc, generate a comprehensive RFC with explicit decision-making sections. This ensures technical proposals capture alternatives, assess risks, and outline migration strategies for team review.

Can I generate a standardized engineering RFC without manually formatting sections?

Yes, you can generate a standardized engineering RFC with automated formatting. The skill enforces best practices like TL;DR summaries, risk assessment tables, and explicit decision-making sections, producing a review-ready document without manual formatting.

Does this RFC drafting approach work for complex service architecture changes?

Yes, this RFC drafting approach works for complex service architecture changes. It produces standardized documents that thoroughly vet system modifications, ensuring technical proposals are comprehensive, risk-aware, and ready for stakeholder sign-off.