rfc

Generate an RFC.md from context.md and an optional PRD.md using a template.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/GomezFabricio/sdd-genesis --skill rfc-gomezfabricio
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: rfc
Source: https://github.com/GomezFabricio/sdd-genesis/tree/main/skills/rfc
Command: npx skills add https://github.com/GomezFabricio/sdd-genesis --skill rfc-gomezfabricio

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill automates the generation of RFC.md from a contextual input (context.md) and an optional PRD.md, providing a structured and ready-to-review technical design document to guide implementation.

Core Features & Use Cases

  • Reads context.md to extract project name, description, version, author, date, and technical motivations.
  • Optionally cross-references an existing PRD.md to enrich the RFC with problem framing, architecture, and deployment details.
  • Applies an RFC template (rfc-template.md) to produce a self-contained RFC.md in the same directory as the inputs.
  • NO folder creation, no number calculation, and no file movement are performed; the RFC is generated in-place for easy review.

Quick Start

Create an RFC.md in the same folder by reading context.md (and an optional PRD.md) and applying an RFC template.

Frequently Asked Questions about rfc

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

FAQPage Schema
How do I generate an RFC document from existing project context and PRD files?

Generate an RFC document by combining a context.md and an optional PRD.md using a predefined template. The structured RFC.md is produced in-place within the same directory as the input files, avoiding any folder creation or file movement.

What is an RFC used for in software architecture and technical design?

An RFC provides a structured technical design document for formalizing architectural decisions early in a project. It captures project descriptions, technical motivations, and deployment details extracted from context and PRD files to guide implementation across new or existing systems.

Do I need a PRD file to create an RFC, or is context.md enough?

A PRD file is optional; a context.md is sufficient to generate an RFC. While context.md provides core project details, cross-referencing an optional PRD.md enriches the RFC with problem framing, architecture, and deployment specifics.

How does this process handle file organization when outputting the RFC?

The RFC generation process enforces in-place output, creating the RFC.md in the exact same directory as the input files. It performs no folder creation, no file movement, and no number calculation, ensuring straightforward review.

Can I use this RFC generation approach for documenting existing systems?

Yes, this RFC generation approach targets both new initiatives and existing systems. It extracts technical motivations and project details from your context.md to produce a ready-to-review architectural decision document for any software project requiring formal documentation.

What limitations exist when generating an RFC from markdown templates?

Limitations include strict in-place generation without creating folders or moving files, and no numerical calculations are performed. The RFC.md output is entirely dependent on the project details and technical motivations provided within your context.md and PRD.md inputs.