What problem does it solve?
Design proposals often jump straight to solutions before the problem is agreed, pad alternatives with strawmen, and leave drawbacks unstated, making them impossible to review meaningfully. This Skill enforces a disciplined, gated workflow for writing RFC-shaped proposals in a markdown knowledge base so every proposal forces a real decision reviewers can disagree with.
Core Features & Use Cases
- Gated problem framing: A mandatory STOP gate requires naming the beneficiary, observable change, and forced decision before any design text is drafted.
- Structured proposal template: Creates numbered files (e.g., proposals/0007-async-export-pipeline.md) from a template with Motivation, Design, Alternatives, Drawbacks, and Unresolved Questions sections.
- Prior-art scanning and validation: Searches existing proposals and decisions to avoid re-litigating accepted decisions, then audits links, frontmatter, and section completeness.
- Use Case: An engineer wants to propose an async export pipeline. The Skill first confirms who benefits and what decision is forced, then drafts a complete RFC with honest alternatives and drawbacks, leaving status as draft for human review.
Quick Start
Ask the agent to frame a proposal for the change you have in mind, for example: frame a proposal for adding an async export pipeline to the project.