What problem does it solve? Design discussions often jump straight to solutions before anyone agrees on the problem, producing RFCs with strawman alternatives and empty drawbacks sections that reviewers cannot meaningfully evaluate. This Skill enforces a gated authoring workflow that frames the beneficiary, observable change, and forced decision before any design text is written. ## Core Features & Use Cases - Gated proposal authoring: A mandatory ten-step workflow (prior-art scan, problem framing STOP gate, sequence allocation, motivation, design, alternatives, drawbacks, unresolved questions, validation, recap) that blocks drafting the Design section before the problem is confirmed. - Template-based creation: Allocates the next zero-padded sequence number and creates the file from the proposal template with correct frontmatter (type, status: draft, authors, created, tags). - Review-quality enforcement: Requires at least two real alternatives with why-not rationale, honest drawbacks, and an unresolved-questions backlog where each entry names resolving evidence and a decider. - Use Case: An engineer wants to propose an async export pipeline. The Skill first scans proposals/ and decisions/ for prior art, confirms the framing (beneficiary, observable change, forced decision) with the user, then drafts proposals/0007-async-export-pipeline.md with all five required sections and validates links via audit. ## Quick Start Ask the agent to frame a design proposal for the change you have in mind, and confirm the beneficiary, observable change, and forced decision when it presents the framing gate.
