rfc-skills

A collection of Claude Code skills that guide the full RFC lifecycle: from initial ideation through drafting, review, finalization, and incorporating feedback. Built on the Anthropic Agent Skills specification.

The Workflow

The skills form a pipeline. Each skill handles one phase of the RFC process.

1. brainstorming-rfc

Explore the problem space before writing. This skill runs a collaborative dialogue, asking questions one at a time to uncover constraints, stakeholders, and alternatives. It produces a structured ideation note that feeds into the next step.

Use this when you have a rough idea but haven't figured out what exactly to propose.

2. writing-technical-docs

Draft the RFC using a write/review loop. Spawns rfc-writer and rfc-reviewer subagents that iterate on the document. The writer follows a detailed style guide; the reviewer checks for quality issues, AI-obvious patterns, and structural problems.

The skill also helps you pick the right document type (PRD vs. RFC vs. Implementation Plan) based on what you're trying to communicate.

3. finalizing-technical-docs

Prepare the draft for circulation. This handles the mechanical cleanup after the content is approved: resolving <!-- REVIEW: ... --> markers, converting ASCII diagrams to mermaid, and removing the Draft Status section.

4. incorporating-rfc-feedback

Process reviewer feedback systematically. Each piece of feedback is evaluated against the RFC's documented constraints, background, and abandoned alternatives before accepting or pushing back.

Installation

/plugin marketplace add lemieux/rfc-skills
/plugin install rfc-skills@lemieux-rfc-skills

Alternative install methods:

• •HTTPS: /plugin marketplace add https://github.com/lemieux/rfc-skills.git
• •Local directory: /plugin marketplace add ./path/to/rfc-skills

Prerequisites

• •Claude Code

What's Included

skills/
├── brainstorming-rfc/              # Pre-RFC exploration
├── writing-technical-docs/    # Core RFC writing workflow
│   └── references/            # Style guide, template, example, reviewer prompt
├── finalizing-technical-docs/ # Pre-circulation cleanup
└── incorporating-rfc-feedback/ # Feedback processing

agents/
├── rfc-writer.md              # Writes/updates RFC drafts
└── rfc-reviewer.md            # Reviews for quality issues

spec/                          # Agent Skills specification docs
template/                      # Starter template for new skills

Writing Quality

The skills enforce specific writing patterns to produce documents that read like they were written by a person, not generated by a model.

What the style guide requires:

• •Direct, professional prose with active voice
• •Connected sentences that flow naturally (not choppy staccato)
• •"We" not "you" throughout
• •Decisions explained with reasoning, not just stated

What the style guide prohibits:

• •Em dashes, hedging phrases ("It's worth noting"), rhetorical questions
• •Bullet-heavy structure where prose would work better
• •Filler sentences that add words without adding information

Links

• •Anthropic Agent Skills Specification