dev-rfc

Create RFCs and technical design documents with structured templates.

193|17|Updated Jan 16, 2026

Search Tags:#architecture #documentation #software development #rfc #design doc #technical proposal

Ready to run

npx skills add https://github.com/pproenca/dot-skills --skill dev-rfc

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: dev-rfc
Source: https://github.com/pproenca/dot-skills/tree/main/skills/.experimental/dev-rfc
Command: npx skills add https://github.com/pproenca/dot-skills --skill dev-rfc

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires open, and includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

This Skill streamlines the creation of well-structured RFCs and technical proposals, ensuring clarity and alignment for software projects.

Core Features & Use Cases

RFC & Architecture Docs: Generate RFCs for new features or Architecture Docs for existing systems.
Template Variety: Supports RFC, Architecture Doc, and One-Pager formats.
Use Case: When proposing a new microservice, use this Skill to draft an RFC that outlines the problem, goals, approaches, and SLAs.

Quick Start

Use the dev-rfc skill to write a new RFC for the user authentication system.

Frequently Asked Questions about dev-rfc

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

FAQPage Schema

How do I write an RFC for a new software feature?▼

To write an RFC for a new software feature, use structured templates that guide you through clear problem statements, goal definitions, approach comparisons, and actionable rollout plans. This ensures technical proposals maintain clarity and alignment across the team.

What is the difference between an RFC and a one-pager technical design doc?▼

An RFC provides comprehensive technical proposal details including approach comparisons and rollout plans, while a one-pager offers a concise format for quickly communicating architectural concepts. Both formats structure problem statements and goals for software projects.

How do I document architecture for an existing system?▼

To document architecture for an existing system, use an Architecture Doc template to outline the current problem context, system goals, and technical approaches. This provides structured guidance to ensure existing infrastructure is clearly communicated.

What should be included in a technical proposal for a microservice?▼

A technical proposal for a microservice should include a clear problem statement, defined goals, compared approaches, SLAs, and an actionable rollout plan. Structured RFC documentation ensures the proposed architecture meets alignment requirements.

When do I need a formal technical design document instead of a one-pager?▼

You need a formal technical design document when proposing complex features requiring detailed approach comparisons and rollout plans. Use a one-pager for simpler architectural concepts that only need a brief problem statement and goal summary.