Create a new RFC (Request for Comments) technical specification
Creates a new RFC technical specification with proper numbering and directory structure.
/plugin marketplace add jpoutrin/product-forge/plugin install devops-data@product-forge-marketplace<rfc-title>Category: Technical Architecture
/create-rfc <rfc-title>
<rfc-title>: Required - Short descriptive title for the RFC (will be kebab-cased for filename)When this command is run, Claude Code should:
Determine RFC Number
rfcs/ directory (all subdirectories) for existing RFC filesCreate Directory Structure (if not exists)
rfcs/
├── draft/
├── review/
├── approved/
│ └── in-progress/
├── completed/
└── archive/
Generate RFC File
rfcs/draft/RFC-XXXX-<kebab-title>.mdPopulate Metadata
rfc_id to new numbertitle from argumentstatus to DRAFTcreated and last_updated to today's dateauthor for user to fillConfirm 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
Use the template from:
plugins/devops-data/skills/rfc-specification/references/rfc-template.md
/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
rfcs/ directory doesn't exist, create it with full structure