What problem does it solve?
RFCs are essential for documenting significant architectural decisions, but teams often struggle with consistency, traceability, and shared understanding. This skill provides a structured approach to writing high-quality RFCs that capture problem context, proposed changes, trade-offs, and implementation plans.
Core Features & Use Cases
- Structured RFC workflow: defines sections for context, decision, consequences, and alternatives.
- Terminology & Boundaries: promotes ubiquitous language and bounded context to ensure alignment across teams.
- Use Case: when a team proposes a major system change (e.g., new service, data model, or deployment approach), use this skill to create a complete RFC package.
Quick Start
Write an RFC for a significant architectural change, including problem statement, proposed solution, alternatives, and rollout plan.