rfc-writer
Write an engineering RFC (Request for Comments) for a technical decision, architectural change, or significant implementation approach. Use when asked to write an RFC, document a technical proposal, create a design doc, write an architecture decision for review, or produce a technical specification for team feedback. Produces a complete RFC document covering problem statement, motivation, proposed solution, alternatives rejected, implementation plan, migration plan, security and performance implications, observability changes, rollout plan, and open questions.
npx skills add mohitagw15856/pm-claude-skills --skill rfc-writer --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# RFC Writer Skill Produce a complete engineering RFC (Request for Comments) for a technical decision or architectural change. An RFC is a structured proposal document — not a persuasion document. Its purpose is to expose a decision to scrutiny, surface trade-offs, document alternatives considered, and create a permanent record of why a choice was made. A good RFC makes it possible for someone who wasn't in the room to understand years later why the team built something the way they did. ## Required Inputs Ask for these if not already provided: - **RFC title and author** — what this RFC is about and who is proposing it - **Problem being solved** — what is broken, missing, or inadequate today; why action is needed now - **Proposed solution** — the approach the author is recommending, at least at a high level - **Context and constraints** — team size, existing architecture, timeline pressures, budget limits, compliance requirements - **Alternatives considered** — at least 2 alternative approaches the author has thought about - **Current status** — is this pre-decision (seeking feedback) or post-decision (documenting a made decision)? ## Output Format --- # RFC [Number]: [Title] **Aut
- Required Inputs
- Output Format
- Abstract
- 1. Problem Statement
- 2. Goals and Non-Goals
- 3. Background and Motivation
- 4. Proposed Solution
- 4.1 High-Level Approach
- 4.2 Architecture
- 4.3 Detailed Design
- 4.4 API Changes
- 4.5 Data Model Changes
- 5. Alternatives Considered
- Alternative 1: [Name]
What does the rfc-writer skill do?
Write an engineering RFC (Request for Comments) for a technical decision, architectural change, or significant implementation approach. Use when asked to write an RFC, document a technical proposal, create a design doc, write an architecture decision for review, or produce a technical specification for team feedback. Produces a complete RFC document covering problem statement, motivation, proposed solution, alternatives rejected, implementation plan, migration plan, security and performance implications, observability changes, rollout plan, and open questions.
How do I install it?
Run `npx skills add mohitagw15856/pm-claude-skills --skill rfc-writer --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From mohitagw15856/pm-claude-skills, a repository with 1,255 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.