What problem does it solve? Technical decisions about architecture, tooling, and process often get made informally and their reasoning is lost, leaving teams unable to revisit or challenge them later. This Skill structures a decision into a contestable RFC record with genuine alternatives, verified facts, and explicit trade-offs before the decision is settled. ## Core Features & Use Cases - Decision Framing: Sharpens a vague problem into a single disagreeable decision statement with an explicit out-of-scope list. - Alternatives Analysis: Evaluates at least two genuine options plus doing nothing, stating costs, risks, and downsides of the recommended option. - Store-Agnostic Authoring: Discovers the target decision store (RFC archive, ADR directory, decision log) and writes the record against its own template and conventions. - Use Case: A team debating whether to adopt pnpm across TypeScript services uses this Skill to produce an RFC weighing pnpm against npm and the status quo, with verified claims separated from assumptions and conditions stated that would change the recommendation. ## Quick Start Ask the agent to draft an RFC proposing a specific technical change, such as adopting trunk-based development, and answer its questions about motivation, constraints, and stakeholders.