Stats
Actions
Tags
Help us improve
Share bugs, ideas, or general feedback.
From rfc123-skills
Converts prose discussions of RFC alternatives into a structured comparison table for reviewers to quickly scan options and trade-offs.
npx claudepluginhub twixes/rfc123How this skill is triggered — by the user, by Claude, or both
Slash command
/rfc123-skills:compare-alternativesThis skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
Convert a prose discussion of options into a comparison table reviewers can
Facilitates Request for Comments (RFC) process for technical proposals and design decisions. Supplies templates, ADR comparisons, best practices, and IETF-adapted guidance.
Writes structured RFC specifications with objective technical analysis of options and trade-offs. Activates for technical specs, design documents, and architecture proposals.
Guides writing RFCs for features, architecture, processes, deprecations, migrations, and standards with workflow: type selection, git research, required sections (summary, problem, solution, alternatives, risks), review management, decision logging, and git commit to docs/rfcs/. Use for proposals needing team buy-in on large changes.
Share bugs, ideas, or general feedback.
Convert a prose discussion of options into a comparison table reviewers can scan in 10 seconds.
The user says "compare the options", "build a table", or the RFC contains phrases like "Option A would …, Option B would …" without a structured comparison. Also good when reviewers are confused about which option does what.
Read the RFC. Call rfc123_get_rfc.
Extract the options. List every distinct alternative the body discusses, in the order they appear. If you can only find one, stop and tell the user — there's nothing to compare.
Pick comparison axes. 4–7 axes typically. Choose axes that actually discriminate between options. Generic axes ("complexity", "cost") often end up with the same value in every cell — prefer specific axes that match the topic (e.g. "supports cross-region", "schema-compat with X", "blast radius if it breaks").
Build the table.
| | Option A | Option B | Option C |
|-----------------------|------------------|------------------|------------------|
| <axis 1> | … | … | … |
Show the user. Get their sign-off on the axes and the cell values before committing. They may know domain facts you don't.
Commit. Insert the table just below the "Alternatives considered"
header if one exists; otherwise insert it as a new "## Alternatives
considered" section. Call rfc123_update_rfc_body with the full new
body and a changeDescription like "Add alternatives comparison table".