Skill

create-rfc

Creates new RFC technical specification Markdown files with auto-incremented IDs, directory structure, metadata, and standard template in rfcs/. Use for architecture proposals and decision docs.

Markdown

documentation

developer-tools

npx claudepluginhub jpoutrin/product-forge --plugin devops-data

Tool Access

This skill uses the workspace's default tool permissions.

Preview

**Category**: Technical Architecture

SKILL.md

Similar Skills

rfc-process

Facilitates Request for Comments (RFC) process for technical proposals and design decisions. Supplies templates, ADR comparisons, best practices, and IETF-adapted guidance.

5 tools

documentation-standards

rfc

Manages architecture RFCs: create populated drafts from conversation and docs context, review existing, list all, update sections, transition status.

5 files

doc

rfc

Guides writing RFCs for features, architecture, processes, deprecations, migrations, and standards with workflow: type selection, git research, required sections (summary, problem, solution, alternatives, risks), review management, decision logging, and git commit to docs/rfcs/. Use for proposals needing team buy-in on large changes.

godmode

Stats

Parent Repo Stars7

Parent Repo Forks0

Last CommitFeb 4, 2026

Actions

View Source View Plugin View on GitHub View README

Help us improve

Share bugs, ideas, or general feedback.

create-rfc

Category: Technical Architecture

Usage

/create-rfc <rfc-title>

Arguments

<rfc-title>: Required - Short descriptive title for the RFC (will be kebab-cased for filename)

Execution Instructions

When this command is run, Claude Code should:

Determine RFC Number
- Scan rfcs/ directory (all subdirectories) for existing RFC files
- Find highest RFC number (RFC-XXXX pattern)
- Increment by 1 for new RFC
- If no RFCs exist, start with RFC-0001

Create Directory Structure (if not exists)

rfcs/
├── draft/
├── review/
├── approved/
│   └── in-progress/
├── completed/
└── archive/

Generate RFC File
- Convert title to kebab-case: "API Gateway Selection" → "api-gateway-selection"
- Create file: rfcs/draft/RFC-XXXX-<kebab-title>.md
- Use template from skill references
Populate Metadata
- Set rfc_id to new number
- Set title from argument
- Set status to DRAFT
- Set created and last_updated to today's date
- Leave author for user to fill

Confirm Creation

Created RFC-XXXX: <title>

Location: rfcs/draft/RFC-XXXX-<kebab-title>.md
Status: DRAFT

Next steps:
1. Fill in the Overview and Problem Statement sections
2. Define your Evaluation Criteria before analyzing options
3. Analyze at least 2 options objectively
4. When ready for review: /rfc-status RFC-XXXX --set REVIEW

Template Reference

Use the template from: plugins/devops-data/skills/rfc-specification/references/rfc-template.md

Example Usage

/create-rfc API Gateway Selection

Creates: rfcs/draft/RFC-0001-api-gateway-selection.md

/create-rfc Database Migration Strategy

Creates: rfcs/draft/RFC-0002-database-migration-strategy.md

Validation

Title must be provided (not empty)
Title should be 2-6 words for clarity
Warn if similar RFC already exists (fuzzy match on title)

Error Handling

If rfcs/ directory doesn't exist, create it with full structure
If title is empty, prompt user for title
If similar RFC exists, ask for confirmation before creating