rfc-proposal-writer
SkillMediaDrafts formal technical Requests for Comments (RFCs) complete with motivation, architecture design, and rollout plan.
Available today. Use it from your connected AI after setup.
No other account needed.
Connect ahel once, and every AI you use reads what you have installed.
Then ask your AI: use the rfc-proposal-writer skill
What this skill tells your AI
The instructions your AI receives, as published by codebygarv/ai-skills in skills/documentation/rfc-proposal-writer/SKILL.md and read by ahel’s review.
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
- Problem Statement & Motivation: What business or engineering pain point requires solving now?
- Proposed Solution & Architecture: System diagrams, API payloads, schema migrations, and sequence flows.
- Non-Goals: Explicitly stating what this proposal will not attempt to solve.
- Security & Privacy Considerations: Auth, PII handling, rate limiting, attack surface.
- Rollout & Migration Strategy: Phased rollout, feature flags, rollback triggers, and monitoring metrics.
Output Format
- Markdown RFC document with formal sections: Summary, Motivation, Detailed Design, Drawbacks, Alternatives Considered, Rollout Plan.
Avoid
- Hand-waving implementation details without concrete data schemas or API payloads.
- Omitting drawbacks and potential operational hazards.
Signals
- GitHub stars
- 25
- Forks
- 1
- Last commit
- Aug 2026
Advanced
- Catalog kind
- skill
- Gateway key
rfc-proposal-writer- Source
- github.com/codebygarv/ai-skills