rfc-to-adr

Extract independent architectural decisions from RFC documents into Nygard-format ADR files.

Updated Apr 21, 2026
One-click install
npx skills add https://github.com/juan-estrada-itti/way-of-work-tools --skill rfc-to-adr
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: rfc-to-adr
Source: https://github.com/juan-estrada-itti/way-of-work-tools/tree/main/skills/rfc-to-adr
Command: npx skills add https://github.com/juan-estrada-itti/way-of-work-tools --skill rfc-to-adr

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Toma un RFC como input y extrae las decisiones arquitectónicas implícitas, generando un ADR por cada una en formato Nygard (Contexto · Decisión · Consecuencias · Status). Identifica cuáles decisiones necesitan PoC/spike antes de commitearse. Resuelve el gap de RFCs grandes que mezclan decisiones: separarlas en ADRs individuales permite versionarlas e iterarlas independientemente. Use when: terminaste un RFC técnico y querés extraer decisiones · el RFC tiene >5 decisiones mezcladas · necesitás ADRs para governance · sos Fase 4 del Taller SDD. Triggers: 'rfc a adr', 'crear adr', 'rfc-to-adr', 'partir rfc', 'adr desde rfc', 'architecture decisions', 'decisiones arquitectura', 'nygard adr', 'extraer adrs'.

Core Features & Use Cases

  • Convierto RFCs grandes en ADRs individuales para cada decisión clave, facilitando versionado y governance.
  • Genero archivos ADR-INDEX.md y ADR-00N-<título>.md en formato Nygard, con referencias al RFC fuente.
  • Identifico decisiones que requieren PoC o spike y etiqueto cada ADR con su criterio de éxito.

Quick Start

Pega el RFC en formato markdown y ejecuta la skill para generar ADRs independientes en docs/04-adrs.

Frequently Asked Questions about rfc-to-adr

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

FAQPage Schema
How do I extract individual architectural decisions from a large RFC document?

Generating an ADR-INDEX.md and individual ADR-00N files in Nygard format requires structuring each extracted decision with Context, Decision, Consequences, and Status sections, while cross-referencing the original RFC and project conventions to maintain traceability.

When do I need to split an RFC into multiple Architecture Decision Records?

You need to split an RFC into multiple Architecture Decision Records when the technical document contains multiple mixed decisions, typically more than five. Partitioning them into individual ADRs allows you to version and iterate on each architectural governance decision independently.

How do I identify which architectural decisions from an RFC require a PoC or spike?

Identifying which architectural decisions require a Proof of Concept (PoC) or spike involves analyzing each extracted ADR for technical risk and labeling it with specific success criteria. This ensures high-risk decisions are validated through experimentation before being committed to governance.

What is the Nygard format for Architecture Decision Records?

The Nygard format for Architecture Decision Records is a structured template that organizes each decision into four sections: Context, Decision, Consequences, and Status. It provides a standardized way to document architectural choices and their impacts for governance.

Can I cross-reference my generated ADRs with existing business PRDs and project conventions?

Cross-referencing generated ADRs with business PRDs and project conventions is supported during the extraction process. The tool relates each Architecture Decision Record to the contract-definition stage and checks CLAUDE.md conventions to ensure alignment with existing technical documentation.