bump-rfc

Automate RFC status transitions across Draft, Planned, In Progress, and Implemented.

92|7|Updated Dec 11, 2025
One-click install
npx skills add https://github.com/dannys-code-corner/incan --skill bump-rfc
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bump-rfc
Source: https://github.com/dannys-code-corner/incan/tree/main/.agents/skills/bump-rfc
Command: npx skills add https://github.com/dannys-code-corner/incan --skill bump-rfc

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Streamlines RFC lifecycle management by automating status bumps, eliminating manual edits and reducing drift between RFCs and their current stage.

Core Features & Use Cases

  • Supports the four standard transitions (Draft → Planned, Planned → In Progress, In Progress → Implemented) with built-in prerequisites checks and guidance for related GitHub actions.
  • Guides contributors through required edits, reviews, and documentation updates to keep RFCs synchronized with project workflow.
  • Use cases include promoting RFCs after approval, updating progress during development, or finalizing implementations for merge-ready status.

Quick Start

Run the bump-rfc command to advance an RFC to the next status.

Frequently Asked Questions about bump-rfc

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate RFC status transitions for project management workflows?

To update an RFC status, the workflow reads the current Status field and applies the appropriate bump across the four standard stages. It validates prerequisites and requires explicit confirmation before applying changes to ensure proper GitHub actions and design decisions are followed.

What are the standard RFC status transitions supported in Incan project workflows?

The standard RFC status transitions supported are Draft to Planned, Planned to In Progress, and In Progress to Implemented. Each transition includes built-in prerequisite checks and guidance for related GitHub actions to keep RFCs synchronized with the project workflow.

Do I need to manually edit RFC files when promoting them after approval?

You do not need to manually edit RFC files when promoting them after approval. The workflow guides contributors through required edits, reviews, and documentation updates automatically, eliminating manual edits and reducing drift between RFCs and their current stage.

How does prerequisite validation work before an RFC status bump is applied?

Prerequisite validation checks required conditions before applying an RFC status bump. The workflow requires explicit confirmation and validates prerequisites to ensure proper GitHub actions and design decisions are followed before advancing the RFC to the next status.

Can I finalize an RFC for merge-ready status after development is complete?

You can finalize an RFC for merge-ready status by transitioning it from In Progress to Implemented. This final status bump guides you through required documentation updates and reviews to ensure the implementation is fully synchronized with project workflow standards.