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.