Agent skill · Documentation

create-rfc

Creates structured Request for Comments (RFC) documents for proposing and deciding on significant changes. Use when the user says "write an RFC", "create a proposal", "I need to propose a change", "draft an RFC", "document a decision", or needs stakeholder alignment before making a major technical or process decision. Do NOT use for TDDs/implementation docs (use technical-design-doc-creator instead), README files, or general documentation.

tech-leads-clubgithub.com/tech-leads-clubGitHub ↗
claude-codecopilotcursorNOASSERTION
Install
npx skills add tech-leads-club/agent-skills --skill create-rfc --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 3
SKILL.md size: 11 KB
Bundled scripts: none
Version: 1.0.0
Declared author: Tech Leads Club - github.com/tech-leads-club
Path: packages/skills-catalog/skills/(creation)/create-rfc/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 4,983
Language: TypeScript
Read our review of the source →

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# RFC Creator You are an expert in creating Request for Comments (RFC) documents that clearly communicate proposals, capture alternatives considered, and drive structured decision-making across teams. ## When to Use This Skill Use this skill when: - User asks to "write an RFC", "create an RFC", "draft a proposal", or "write a request for comments" - User needs to propose a significant change and gather stakeholder feedback - A major architectural, process, or product decision needs to be documented before acting - User wants to align multiple teams or approvers before committing to a direction - User asks to "document a decision" or "get buy-in" on a proposal - User needs to compare options and record the chosen direction with rationale Do NOT use for: - Technical Design Documents focused on implementation (use `technical-design-doc-creator`) - Simple meeting notes or summaries - README files or API documentation ## Language Adaptation **CRITICAL**: Always generate the RFC in the **same language as the user's request**. Detect the language automatically and generate all content in that language. - Keep technical terms in English when appropriate (e.g., "API", "RFC", "rollback", "st

What's inside
Steps it walks through
  1. When to Use This Skill
  2. Language Adaptation
  3. RFC vs TDD
  4. Interactive Workflow
  5. Step 1: Gather Context (if not provided)
  6. Step 2: Validate Mandatory Fields
  7. Step 3: Detect RFC Type and Tailor Sections
  8. Step 4: Generate RFC Document
  9. Step 5: Offer Next Steps
  10. Document Structure
  11. Mandatory Sections
  12. Recommended Sections
  13. Section Templates
  14. RFC Quality Checklist
Ships with 2 files
  • README.md
  • references/section-templates.md
More from agent-skills
All skills →
About this skill
What does the create-rfc skill do?

Creates structured Request for Comments (RFC) documents for proposing and deciding on significant changes. Use when the user says "write an RFC", "create a proposal", "I need to propose a change", "draft an RFC", "document a decision", or needs stakeholder alignment before making a major technical or process decision. Do NOT use for TDDs/implementation docs (use technical-design-doc-creator instead), README files, or general documentation.

How do I install it?

Run `npx skills add tech-leads-club/agent-skills --skill create-rfc --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 tech-leads-club/agent-skills, a repository with 4,983 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.

Keep going