Can I use this for minor code changes?

While possible, it is best suited for high-impact design decisions; smaller changes are typically better handled via standard pull request descriptions or smaller internal notes.

How does this skill help with team consensus?

It structures feedback loops and requires documentation of alternatives and drawbacks, ensuring objections are addressed and documented rather than ignored during the review process.

Is this skill based on any specific industry standards?

Yes, it is grounded in proven models like the Rust RFC process, Internet RFCs, and Architecture Decision Records (ADRs) by Michael Nygard.

When should I use the RFC Template skill?

Use this skill when proposing major architectural changes, introducing new frameworks, or making design decisions that impact multiple teams or long-term maintainability.

What are the key sections included in the generated RFC?

The template includes a problem statement, proposed solution, detailed design, alternatives considered, drawbacks, risks, and an implementation plan.

Architectural RFC Template

Name: Architectural RFC Template
Author: sethdford

bysethdford

•

Collaboration Tools

Generates comprehensive Request for Comments (RFC) documents to propose, discuss, and finalize major architectural changes.

The Architectural RFC Template skill helps engineering teams move from informal ideas to structured, collaborative decision-making by providing a standardized framework for architectural proposals. It guides Claude to document the problem statement, technical design, alternatives considered, and potential risks, ensuring all stakeholders are aligned before implementation begins. Grounded in industry standards like the Rust RFC process and Architecture Decision Records (ADRs), this skill is essential for technical leads and architects who need to build consensus and maintain a clear audit trail of technical debt and design choices.

Key Features

01Standardized RFC headers for tracking status, authors, and related issues

02Built-in anti-pattern detection to prevent vague proposals or late-stage feedback

035 GitHub stars

04Detailed design structure for APIs, data structures, and state management

05Quantifiable problem impact analysis covering latency, cost, and productivity

06Systematic evaluation of alternatives and trade-offs to justify decisions

Use Cases

01Documenting major breaking changes in shared libraries or internal APIs

02Proposing a migration from a monolithic architecture to microservices

03Introducing new design patterns or core technology stacks to an engineering team

Key Features

01Standardized RFC headers for tracking status, authors, and related issues

02Built-in anti-pattern detection to prevent vague proposals or late-stage feedback

035 GitHub stars

04Detailed design structure for APIs, data structures, and state management

05Quantifiable problem impact analysis covering latency, cost, and productivity

06Systematic evaluation of alternatives and trade-offs to justify decisions

Use Cases

01Documenting major breaking changes in shared libraries or internal APIs

02Proposing a migration from a monolithic architecture to microservices

03Introducing new design patterns or core technology stacks to an engineering team