From devops-data
Displays RFC details or updates status through lifecycle (DRAFT to COMPLETED), manages reviewers/comments, validates transitions, and moves files in rfcs/ directories.
npx claudepluginhub jpoutrin/product-forge --plugin devops-dataThis skill uses the workspace's default tool permissions.
**Category**: Technical Architecture
Facilitates Request for Comments (RFC) process for technical proposals and design decisions. Supplies templates, ADR comparisons, best practices, and IETF-adapted guidance.
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.
Share bugs, ideas, or general feedback.
Category: Technical Architecture
/rfc-status <rfc-id> [options]
<rfc-id>: Required - RFC identifier (e.g., RFC-0042 or just 0042)| Option | Description |
|---|---|
--set <status> | Transition to new status |
--reviewer <name> | Add or update reviewer |
--comment <text> | Add status change comment |
DRAFT - Initial writingREVIEW - Open for feedbackAPPROVED - Decision madeIN_PROGRESS - Implementation startedCOMPLETED - Implementation finishedREJECTED - Proposal declinedABANDONED - Author withdrewSUPERSEDED - Replaced by newer RFCWhen viewing an RFC:
Find the RFC file
rfcs/ subdirectoriesDisplay RFC Details
RFC-0042: Database Migration Strategy
======================================
Status: REVIEW
Author: Jane Doe
Created: 2025-12-01
Updated: 2025-12-05
Location: rfcs/review/RFC-0042-database-migration-strategy.md
Reviewers:
- Alice Chen: approved (2025-12-04)
- Bob Smith: pending
- Carol Wu: in-progress
Overview:
[First 2-3 sentences of the Overview section]
Valid Transitions:
→ APPROVED (requires all reviewers approved)
→ DRAFT (needs revision)
→ REJECTED (proposal declined)
Commands:
/rfc-status RFC-0042 --set APPROVED
/rfc-status RFC-0042 --reviewer "Bob Smith:approved"
When updating status:
Validate Transition
Valid transitions:
| From | To |
|---|---|
| DRAFT | REVIEW, ABANDONED |
| REVIEW | APPROVED, REJECTED, DRAFT |
| APPROVED | IN_PROGRESS, SUPERSEDED |
| IN_PROGRESS | COMPLETED, SUPERSEDED |
| Any | SUPERSEDED (with link to new RFC) |
Perform Pre-transition Checks
For REVIEW → APPROVED:
For APPROVED → IN_PROGRESS:
For IN_PROGRESS → COMPLETED:
Update RFC File
status in frontmatterlast_updated to todaydecision_date if transitioning to APPROVEDarchive_date if archivingMove File to Correct Directory
| Status | Directory |
|---|---|
| DRAFT | rfcs/draft/ |
| REVIEW | rfcs/review/ |
| APPROVED | rfcs/approved/ |
| IN_PROGRESS | rfcs/approved/in-progress/ |
| COMPLETED | rfcs/completed/ |
| REJECTED | rfcs/archive/YYYY/rejected/ |
| ABANDONED | rfcs/archive/YYYY/abandoned/ |
| SUPERSEDED | rfcs/archive/YYYY/superseded/ |
Confirm Update
RFC-0042 status updated: REVIEW → APPROVED
Updated:
- Status: APPROVED
- Decision Date: 2025-12-06
- Location: rfcs/approved/RFC-0042-database-migration-strategy.md
Next steps:
1. Create implementation tasks
2. When starting work: /rfc-status RFC-0042 --set IN_PROGRESS
Update reviewer status:
/rfc-status RFC-0042 --reviewer "Bob Smith:approved"
/rfc-status RFC-0042 --reviewer "Carol Wu:declined"
Reviewer statuses:
pending - Not yet reviewedin-progress - Currently reviewingapproved - Approved the RFCdeclined - Requested changes or rejected# View RFC details
/rfc-status RFC-0042
# Submit for review
/rfc-status RFC-0042 --set REVIEW
# Approve RFC
/rfc-status RFC-0042 --set APPROVED --comment "All concerns addressed"
# Start implementation
/rfc-status RFC-0042 --set IN_PROGRESS
# Mark complete
/rfc-status RFC-0042 --set COMPLETED
# Mark as superseded
/rfc-status RFC-0042 --set SUPERSEDED --comment "Replaced by RFC-0050"
git mv)When transitioning to IN_PROGRESS:
/generate-tasks if PRD linkedWhen transitioning to COMPLETED: