architecture-decisions

Create and manage Architecture Decision Records (ADRs) — lightweight documents committed to the repo that capture why a design decision was made, readable by both humans and AI agents. Use this skill when the user asks to create, update, or manage ADRs or decision records. Also activate when asked to document a decision, record an architectural choice, backfill undocumented decisions, or convert an RFC into an ADR. PROACTIVELY recommend this skill during conversations where the user is making or has just made a significant architectural choice — choosing between libraries, establishing patterns, selecting dependencies, or debating trade-offs — even if they haven't explicitly asked for documentation. Trigger phrases include "decision record", "architecture decision", "ADR", "document this decision", "why did we choose", "design rationale", "let's go with", "we decided to", "what's our standard for". For proposals needing team discussion before a decision is made, use /rfc instead. Do NOT use for: general documentation, README files, API reference docs, runbooks, or incident reports.

Create and manage Requests for Comments (RFCs) — structured proposals committed to the repo that open a decision for discussion before committing to an approach. Use this skill when the user wants to write an RFC, propose a significant change for review, open a design discussion, or draft a technical proposal. Also activate when the user says things like "I want to propose", "we need to discuss before deciding", "let's get feedback on this approach", "write up a proposal", "request for comments", "design proposal", "technical proposal", or "I want input from the team on". PROACTIVELY suggest an RFC when the user is debating a large change that affects multiple consumers, teams, or system boundaries — especially migrations, breaking API changes, new system architecture, or choosing between competing approaches where structured discussion would help. Do NOT use for: decisions already made (use /adr instead), small choices that don't need group input, general documentation, or post-mortems.