Individual skill
rfc-proposal-writer
Drafts formal technical Requests for Comments (RFCs) complete with motivation, architecture design, and rollout plan.
skills/documentation/rfc-proposal-writer/SKILL.md
Source commit d0a9928d24afb7df0fad2f2f35f65d3938a6926a
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- No
- Repository scan complete
- No
- Skill scan complete
- Yes
- Observed behavior
- Not checked yet
- Last checked
- Nov 5, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 27
- Repository last updated
- Aug 20, 2026
- License
- MIT
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- claude-code Repository topic
- ai Repository topic
- ai-agents Repository topic
- ai-coding Repository topic
- ai-skill Repository topic
- ai-skill-enhancement Repository topic
- ai-skills Repository topic
- ai-skills-analysis Repository topic
- ai-skills-fest Repository topic
- ai-skills-manager Repository topic
- engineering Derived category
- design Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
README.mddoc · 572 bytesSKILL.mdcore · 1,513 bytesexamples/example.mddoc · 1,169 bytes
Read excerpt
## Purpose
Author comprehensive, highly structured Request for Comments (RFC) engineering proposals that clearly articulate the motivation, technical design, alternatives considered, security implications, and rollout phases for major technical initiatives.
## When to Use
- Proposing large architectural refactors, new microservices, or shared libraries.
- Introducing major third-party vendors or new programming languages to the stack.
- Building consensus across distributed engineering teams before writing code.
## What to Analyze
1. **Problem Statement & Motivation**: What business or engineering pain point requires solving now?
2. **Proposed Solution & Architecture**: System diagrams, API payloads, schema migrations, and sequence flows.