rfc-research

Generate RFC documents with evidence from GitHub code via octocode MCP.

10|1|Updated Mar 10, 2026

Search Tags:#architecture #research #github #decision record #rfc #technical proposal

Ready to run

npx skills add https://github.com/vltansky/skills --skill rfc-research

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: rfc-research
Source: https://github.com/vltansky/skills/tree/main/skills/rfc-research
Command: npx skills add https://github.com/vltansky/skills --skill rfc-research

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the creation of RFC (Request for Comments) documents by grounding technical proposals in real-world code evidence from GitHub, moving beyond theoretical discussions to data-driven decision-making.

Core Features & Use Cases

Evidence-Based Proposals: Generates RFCs with claims directly linked to GitHub code, PRs, and repository structures.
Automated Research: Leverages tools like octocode MCP to search repositories, analyze code, and synthesize findings.
Structured RFC Format: Adheres to a standard RFC template covering problem, context, proposal, alternatives, risks, and references.
Use Case: When proposing a new API design, use this Skill to research how similar problems are solved in popular open-source projects, providing concrete examples and trade-offs to inform your decision.

Quick Start

Write an RFC for migrating our API layer from REST to GraphQL.

Frequently Asked Questions about rfc-research

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

FAQPage Schema

How do I write an RFC with real code evidence from GitHub?▼

To write a technical proposal with real code evidence, this Skill researches GitHub repositories using octocode MCP and generates structured RFC documents grounded in verifiable code references, analyzing prior art, alternatives, and risks.

What is an evidence-based technical proposal in software architecture?▼

An evidence-based technical proposal is an RFC document where architectural decisions are supported by real-world code examples, PRs, and repository structures from GitHub rather than theoretical discussions, ensuring data-driven decision-making.

Do I need octocode MCP server to generate RFC documents?▼

Yes, you need the octocode MCP server configured for GitHub API access and code analysis tools to enable the Skill to search repositories, analyze code, and synthesize findings for RFC generation.

Can I research how open-source projects solve similar architecture problems for my decision record?▼

Yes, you can research how similar problems are solved in popular open-source projects by having the Skill search repositories and analyze code, providing concrete examples and trade-offs to inform your decision record.

What is the best way to structure an RFC for migrating an API layer?▼

The best way to structure an RFC for an API migration is using a standard template covering the problem, context, proposal, alternatives, risks, and references, which this Skill generates automatically with supporting GitHub evidence.

What are the limitations of using automated research for technical proposals?▼

The automated research for technical proposals relies entirely on the octocode MCP server configuration for GitHub API access, meaning it cannot analyze code or synthesize findings without this dependency properly set up in your environment.