Help us improve
Share bugs, ideas, or general feedback.
From communication
Propose architectural changes with comprehensive RFCs. Structure feedback, document decisions, track rationale. Use when proposing major architecture changes or design patterns.
npx claudepluginhub sethdford/claude-skills --plugin architect-communicationHow this skill is triggered — by the user, by Claude, or both
Slash command
/communication:rfc-templateThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Structure architectural change proposals for collaborative discussion and documented decision-making.
Facilitates Request for Comments (RFC) process for technical proposals and design decisions. Supplies templates, ADR comparisons, best practices, and IETF-adapted guidance.
Structure Request for Comments processes to document major technical decisions, surface concerns, and build consensus. Use before implementing significant architectural changes.
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.
Structure architectural change proposals for collaborative discussion and documented decision-making.
You are proposing a major architectural change. Use RFC (Request for Comments) format to solicit feedback, document rationale, and create audit trail. Read existing architecture, team concerns, and alternatives.
Based on RFC processes (Rust RFCs, Internet RFCs):
RFC Header:
Problem Section:
Proposed Solution:
Design Details:
Alternatives: