octocode-rfc-generator

star 863

Research-driven RFC and design document generator. Use when the user asks to "create an RFC", "write a design doc", "propose a migration", "how should we architect X", "evaluate options for X", "write a technical proposal", "compare approaches", or needs a technical decision document before coding. Outputs a validated RFC with research evidence, alternatives, recommendation, and implementation plan. For planning with implementation, use octocode-plan instead.

bgauryy By bgauryy schedule Updated 3/11/2026
play_arrow Run Skill in Manus View GitHub

name: octocode-rfc-generator description: "Use when you need an RFC, design doc, architecture proposal, migration plan, implementation plan, or research-backed technical decision before coding. Leverages Octocode local/GitHub/npm/binary tools via MCP or CLI to gather evidence, compare alternatives, map blast radius, and produce a validated RFC with a practical implementation plan."

Octocode RFC Generator

Use this skill when a change needs thinking before coding: architecture choices, migrations, cross-package changes, risky refactors, implementation plans, or formal RFC/design docs. The output is evidence-backed and actionable, not a brainstorm.

Core flow:

UNDERSTAND → RESEARCH → COMPARE OPTIONS → WRITE RFC / PLAN → VALIDATE → DELIVER

If the task is a trivial one-file edit with no design choice, say an RFC is unnecessary and suggest using octocode-engineer directly.

How to run this skill

  1. Frame the work. Read references/workflow.md first, before researching — it defines mode selection (RFC / Plan / Decision / Migration / Validation), the understand checklist, option comparison, the validation gate, and delivery format.

  2. Gather cited evidence. While researching current state, prior art, packages, history, or binaries, follow references/research-playbook.md for the exact MCP/CLI tool map per evidence type, the per-scenario research tracks, evidence-citation rules, and recovery moves when a search comes up empty.

  3. Write the document. When producing a full RFC, copy the body sections (Summary through Prior Art) from references/rfc-template.md. After drafting the body, append the closing sections from references/rfc-implementation.md (Unresolved Questions, Future Possibilities, References, Implementation Plan). For a lighter implementation plan, use the trimmed plan skeleton in references/workflow.md instead of the full template.

Non-negotiables

  • Do not guess facts that tools can verify; cite local claims with file:line and external claims with a GitHub path/line or PR/commit link.
  • Always compare at least two alternatives unless the user explicitly asks for a single implementation plan.
  • Order implementation steps by dependency, not preference; avoid time estimates.
  • Default output location when saving is approved: .octocode/rfc/RFC-{meaningful-name}.md. Ask before saving; otherwise keep the document in chat.
Install via CLI
npx skills add https://github.com/bgauryy/octocode --skill octocode-rfc-generator
Repository Details
star Stars 863
call_split Forks 73
navigation Branch main
article Path SKILL.md
Occupations
Computer Systems Analysts
More from Creator
bgauryy
bgauryy Explore all skills →