Help us improve
Share bugs, ideas, or general feedback.
From rfc123-skills
Walks through an RFC in depth — reads the proposal, grounds discussion threads, and current codebase to surface gaps, edge cases, and contradictions. Posts comments only on user request.
npx claudepluginhub twixes/rfc123How this skill is triggered — by the user, by Claude, or both
Slash command
/rfc123-skills:discuss-rfcThis skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
Help the user think through a specific RFC by grounding the conversation in
Drafts a new RFC from a one-paragraph brief, walking through Background → Proposal → Alternatives → Open questions, then opens a pull request via the RFC123 MCP server.
Facilitates Request for Comments (RFC) process for technical proposals and design decisions. Supplies templates, ADR comparisons, best practices, and IETF-adapted guidance.
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.
Help the user think through a specific RFC by grounding the conversation in both the proposal and the codebase it touches. Surface gaps the author missed. Only post back to the RFC when the user explicitly asks.
The user says "help me think about this RFC", "discuss RFC #N", "review this proposal with me", or pastes an RFC URL and wants to engage with it.
Read the RFC and its discussion. Call rfc123_get_rfc for the body,
rfc123_get_rfc_comments for general comments, and
rfc123_list_review_threads for inline discussion. Skim all three before
forming an opinion.
Ground in the codebase. If the RFC proposes changes to code, locate the files / modules / APIs it touches in the current repository (or repositories it depends on). Read enough to know the current state, not just the proposed state. Skip this step for non-code RFCs (process, policy, organizational).
Surface gaps. Compare the proposal against reality and list:
Hand the conversation to the user. They might want to push back,
brainstorm alternatives, dig into a specific section, or just understand
something. Don't lecture — ask what they want to focus on. Whenever you
need a choice or clarification from the user — at this hand-off or anywhere
later in the conversation — prefer your structured question-asking tool
(e.g. AskUserQuestion in Claude Code) over a plain prose question, so the
user can answer with one click. Fall back to free-text questions only if
no such tool is available.
Post only when asked. When the user says "comment this", "post this as a reply", or similar, route to the right tool:
rfc123_post_general_comment.rfc123_post_inline_comment. line
refers to the PR head file; pass startLine+line for a range.rfc123_submit_review (bundles into one notification). For
REQUEST_CHANGES pass confirmBlocksMerge: true.rfc123_reply_to_comment, with
andResolve: true when the reply also closes the discussion.
RFC123 appends a — via Claude on RFC123 footer automatically; don't
add it yourself.propose-revision.