octocode-rfc-generator

Generates evidence-backed RFCs, design docs, and implementation plans from code research.

921|75|Updated Jun 5, 2025
One-click install
npx skills add https://github.com/bgauryy/octocode-mcp --skill octocode-rfc-generator
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: octocode-rfc-generator
Source: https://github.com/bgauryy/octocode-mcp/tree/main/skills/octocode-rfc-generator
Command: npx skills add https://github.com/bgauryy/octocode-mcp --skill octocode-rfc-generator

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Consequential code changes fail when decisions live only in chat: alternatives disappear, assumptions go untested, and rollback plans are discovered too late. This Skill turns research into a reviewable decision document before risky work begins.

Core Features & Use Cases

  • Decision Documents: Writes RFCs, design docs, architecture proposals, migration plans, and option comparisons with goals, non-goals, alternatives, and pre-mortem analysis.
  • Evidence-Backed Claims: Gathers current-state proof from local code, GitHub paths, PRs, commits, and packages via Octocode, citing exact file:line anchors for every recommendation.
  • Structured Artifact Set: Produces RFC.md, PREREQUISITES.md, IMPLEMENTATION.md, KPI.md, and RESOURCES.md under .octocode/rfc/{name}/ with dependency-ordered steps, rollout/rollback plans, and measurable success criteria.
  • Use Case: Before migrating a production database schema, ask the agent to compare migration strategies, document current-state constraints, and produce an RFC with a phased rollout plan and rollback triggers that reviewers can approve.

Quick Start

Ask the agent to write an RFC for your planned change, for example: draft an RFC comparing two approaches for migrating our authentication service, with evidence from the current codebase.

Frequently Asked Questions about octocode-rfc-generator

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

FAQPage Schema
How do I write an RFC with AI before starting a code change?

Invoke the skill with your proposed change and it runs a structured flow: understand the decision, research evidence with Octocode, compare at least two alternatives, then write the RFC with goals, risks, rollout, and rollback. Small reversible changes produce a single RFC.md; larger work produces a full document set.

What documents does an RFC generator produce for a migration plan?

For non-trivial work it creates a folder under .octocode/rfc/{name}/ containing RFC.md (the decision), PREREQUISITES.md (readiness for existing code), IMPLEMENTATION.md (dependency-ordered build plan), KPI.md (acceptance and success metrics), and RESOURCES.md (source inventory).

Does the RFC skill require Octocode research to work?

Yes, evidence claims are delegated to the octocode-research skill, which handles tool routing, citations, and confidence grading. If it is not installed, the skill points you to install it with npx octocode skill --name octocode-research.

When should I not use an RFC generator for a code change?

Skip RFC mode for trivial one-file edits, which route to octocode-research instead. If the idea is still open-ended and worth-building is unresolved, use octocode-brainstorming first; handoffs marked Prototype First, Narrow, or Park are rejected.

Can the skill review or clean up existing RFCs in my repo?

Yes, it audits existing RFCs against live code, classifies them as implemented, partial, not implemented, or superseded, and writes a dated Audit Reasoning block with file:line evidence. Deletion or archival always requires explicit approval.