[Proposal Title]
The Context
Describe the circumstances that led to this proposal. Give enough background that someone unfamiliar with the area can understand why the work matters. State what you were trying to accomplish, not what solution you reached for first.
The Problem Statement
State the specific problem, limitation, or gap being addressed. Be concrete. A reader should be able to confirm whether a proposed solution actually solves it.
Describe how your proposal will work with code, pseudo-code, mock-ups, or diagrams
Detail the proposed solution precisely enough that it could be implemented without improvising the design. Include code, diagrams, or examples where they reduce ambiguity. Vague or underspecified proposals cannot be acted on.
The Benefits
Describe the concrete improvements this proposal delivers and to whom.
The Downsides
Describe the costs, risks, or trade-offs. Every proposal has them.
The Road Not Taken
Describe the alternatives considered and why this approach was chosen over them.
The Infrequent Use Case
Describe any edge cases or less common scenarios where the proposal behaves differently or does not apply.
In Core and Done by Us
Confirm whether this is core functionality the team will implement, and who owns it.
Status
Status: Draft
Decision Makers
- [Name or role]