One-click install
npx skills add https://github.com/ejoongseok/claude-settings --skill rfc-ejoongseok
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: rfc
Source: https://github.com/ejoongseok/claude-settings/tree/main/claude-code/skills/rfc
Command: npx skills add https://github.com/ejoongseok/claude-settings --skill rfc-ejoongseok

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you replace vague “let’s discuss” moments with a decision request document that clearly lays out multiple unresolved options and the trade-offs, so stakeholders can align quickly and transparently.

Core Features & Use Cases

  • Multi-option decision framing: Generate 2–3 or more options with their pros, cons, trade-offs, and confidence levels for both technical and non-technical choices.
  • Single-file decision workflow: Accumulate feedback revisions and capture the final decision in the same document (rather than spawning separate artifacts like ADRs).
  • Project-context evaluation: Assess options using available project rules, modules, customer impact, and infrastructure constraints when present.

Quick Start

Ask the AI to create an RFC by providing your decision question, the relevant context, and at least two candidate options, and request that it include a recommended option plus a section for collecting feedback and recording the final decision.

Frequently Asked Questions about rfc

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

FAQPage Schema
How do I write a decision request RFC with multiple options and trade-offs?

To write a decision request RFC, provide your decision question, relevant project context, and at least two candidate options. The Skill generates a document unfolding each option's pros, cons, trade-offs, and a final recommendation for stakeholder alignment.

What is the best way to document technical trade-offs for stakeholder alignment?

Documenting technical trade-offs for stakeholder alignment involves framing multiple options with their respective pros, cons, and confidence levels. This approach evaluates options against project rules, modules, and infrastructure constraints to recommend a clear direction.

Can I use a single RFC document for feedback revisions and recording the final decision?

Yes, you can use a single RFC document to accumulate feedback revisions and capture the final decision. This maintains one continuous artifact rather than spawning separate decision records or documents for each update.

How does an RFC differ from an ADR for project documentation?

An RFC differs from an ADR by maintaining a single document that accumulates feedback revisions and records the final decision, whereas ADRs typically spawn separate artifacts. RFCs focus on unfolding multiple unresolved options with trade-offs before a direction is finalized.

Does this RFC process work for non-technical project decisions?

Yes, this RFC process works for non-technical project decisions. It generates a decision request document with multiple options, trade-offs, and confidence levels suitable for team, PM, leadership, and peer discussions requiring alignment.

How do I update an existing RFC instead of creating a new one?

To update an existing RFC, the Skill handles update-versus-new creation modes by applying your new context to the current document. This ensures feedback revisions and final decision details are maintained in one continuous file.