technical-rfc

Generates structured RFC documents for architectural and process changes.

2|1|Updated Feb 27, 2026
One-click install
npx skills add https://github.com/Kaakati/sdh-claude-skills --skill technical-rfc
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: technical-rfc
Source: https://github.com/Kaakati/sdh-claude-skills/tree/main/.claude/skills/technical-rfc
Command: npx skills add https://github.com/Kaakati/sdh-claude-skills --skill technical-rfc

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill provides a structured process for proposing and documenting significant technical changes, ensuring thorough review and team consensus before implementation.

Core Features & Use Cases

  • Structured Proposal Generation: Guides users through writing comprehensive RFCs covering problem statements, solutions, alternatives, and impact assessments.
  • Decision Facilitation: Promotes informed decision-making by requiring detailed research and consideration of various factors.
  • Use Case: When a team needs to decide whether to adopt a new database technology, migrate a major service, or introduce a new architectural pattern, this skill ensures the proposal is well-documented and reviewed.

Quick Start

Use the technical-rfc skill to write a new RFC for migrating our authentication service.

Frequently Asked Questions about technical-rfc

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

FAQPage Schema
How do I write a technical RFC for architectural changes?

To write a technical RFC for architectural changes, you need a structured template covering problem definition, solution design, impact assessment, alternatives, and migration plans. This documentation ensures thorough team review and consensus before implementation begins.

What should be included in a technical design document for migrating a service?

A technical design document for migrating a service should include a problem statement, solution design, impact assessment, alternatives considered, and detailed migration plans. This structured documentation facilitates informed team decision-making and comprehensive review.

When do I need to create an RFC for a new dependency?

You need to create an RFC for a new dependency when proposing significant technical changes that require team consensus. Documenting the proposal ensures thorough research and informed decision-making before introducing new technologies or shifting architectural processes.

How does an RFC template facilitate team review and consensus?

An RFC template facilitates team review and consensus by requiring detailed research and structured documentation across problem statements, solutions, and impact assessments. This standardized format promotes informed decision-making by ensuring all relevant technical factors are systematically considered.

What is the best way to propose a new architectural pattern to my team?

The best way to propose a new architectural pattern is to generate a comprehensive technical proposal document. This structured approach covers problem definition, solution design, and impact assessment, ensuring your proposal is well-documented and thoroughly reviewed before team adoption.