rfc-adr

Create standardized ADR.md files under docs/specs/{feature}/adr.md with required sections.

23|7|Updated Feb 14, 2026
One-click install
npx skills add https://github.com/kinncj/MAPLE --skill rfc-adr
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: rfc-adr
Source: https://github.com/kinncj/MAPLE/tree/main/template/.opencode/skills/rfc-adr
Command: npx skills add https://github.com/kinncj/MAPLE --skill rfc-adr

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Architectural decisions are often scattered across documents, making traceability and governance difficult. This Skill provides a standardized way to create, store, and reference Architecture Decision Records (ADRs) that capture context, alternatives, and outcomes.

Core Features & Use Cases

  • Standardized ADR format stored under docs/specs/{feature}/adr.md to preserve decision history.
  • Lifecycle guidance from proposal to acceptance, re-evaluation, or supersession to ensure decisions stay current.
  • Collaborative governance by enabling teams to document context, constraints, trade-offs, and next steps for future work.

Quick Start

Create the first ADR for a major architectural decision by drafting an adr.md in docs/specs/your-feature and filling in the required sections.

Frequently Asked Questions about rfc-adr

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

FAQPage Schema
How do I document architectural decisions for better governance?▼

Document architectural decisions by creating Architecture Decision Records (ADRs) that capture context, alternatives, and outcomes to ensure traceability. ADRs provide a standardized way to store and reference decision history, solving the problem of scattered architectural documentation.

What sections should be included in an Architecture Decision Record?▼

An Architecture Decision Record should include sections for Status, Context, Goals, Alternatives, Trade-offs, and Next Steps. This standardized format ensures decisions are traceable and enables collaborative governance across teams.

How do I organize ADR files within my project repository?▼

Organize ADR files by storing them as adr.md files under the docs/specs/{feature}/adr.md directory path. This structure preserves decision history by linking architectural decisions directly to their corresponding feature or project folders.

What is the lifecycle of an Architecture Decision Record?▼

The ADR lifecycle flows from proposal to acceptance, re-evaluation, or supersession to ensure architectural decisions stay current. Lifecycle guidance helps teams manage when decisions need to be revisited or replaced over time.

When do I need to create an ADR for my software project?▼

Create an ADR whenever a significant architectural decision is made that impacts future development. ADRs are needed when decisions involve trade-offs, constraints, and alternatives that future team members must understand for effective governance.

Does this ADR approach work for team collaboration and governance?▼

Yes, ADRs enable collaborative governance by allowing teams to document context, constraints, and trade-offs for future work. The standardized format under docs/specs/ ensures all team members can reference and trace architectural decisions.