What problem does it solve? Teams often jump straight from a specification to implementation without systematically comparing alternatives, leading to poorly justified architecture choices. This Skill structures the Request for Comments process so consequential technical or content-system decisions are documented, compared, and reviewed before an ADR or implementation begins. ## Core Features & Use Cases - Structured RFC Authoring: Guides creation of an RFC that links the source specification, restates the decision, and documents constraints and decision drivers. - Alternatives Comparison: Requires at least two viable alternatives plus the status quo, compared across architecture, delivery, cost, performance, security, operations, migration, rollback, teardown, and ownership. - Review and Acceptance Workflow: Separates reviewer feedback from author responses and marks the RFC accepted only after the accountable owner chooses a direction, then creates or updates the corresponding ADR. - Use Case: After writing a specification for a new data pipeline, use this Skill to draft an RFC comparing a streaming versus batch approach, collect review feedback, and hand off the accepted direction to an ADR. ## Quick Start Create an RFC for the decision described in my specification document, comparing at least two alternatives plus the status quo.
