Add a proposal template

README.md

@@ -6,7 +6,7 @@ Think of things like a context API, async work (Suspense-like), SSR-interop, inc
 
 ## Get involved
 
-Check out the [Issues](https://github.com/webcomponents/community-protocols/issues) and [PRs](https://github.com/webcomponents/community-protocols/pulls) currently open on this repo to join in on conversations already inflight regarding a number of exciting areas. If you have ideas on a protocol you like raised to the community open a new [issues](https://github.com/webcomponents/community-protocols/issues/new) so that authors and consumers of libraries and components from across the community that likely have (or wanted to have) implemented features in that area can join in with their use cases as well. Once the rough edges have been hammered out, submit a PR with specs of the protocol and append it to the "Protocols" list below so it can be formalized and put into use across the community.
+Check out the [Issues](https://github.com/webcomponents/community-protocols/issues) and [PRs](https://github.com/webcomponents/community-protocols/pulls) currently open on this repo to join in on conversations already inflight regarding a number of exciting areas. If you have ideas on a protocol you like raised to the community open a new [issues](https://github.com/webcomponents/community-protocols/issues/new) so that authors and consumers of libraries and components from across the community that likely have (or wanted to have) implemented features in that area can join in with their use cases as well. Once the rough edges have been hammered out, submit a PR (pull-request) with specs of the protocol and append it to the "Protocols" list below so it can be formalized and put into use across the community. Use this [template](./proposal-template.md) for your proposals PRs.
 
 ## Proposals
 

proposal-template.md

@@ -0,0 +1,41 @@
+# Proposal name
+
+**Author**: Name here
+
+**Status**: Draft
+
+**Created**: Date here
+
+**Last updated**: Date here
+
+# Summary
+
+A brief, one or two sentence explanation of the proposal.
+
+# Example
+
+Provide an example of the API using type definitions and/or code example.
+
+# Goals
+
+- Write an explicit list.
+- Of what this proposal hopes to achieve.
+- Be as specific and broad as possible.
+
+# Non-goals
+
+- It's also important to be explicit about non-goals.
+- This prevents feature creep and tangent conversations.
+- Both goals and non-goals are valid topics to debate and can make/break the proposal.
+
+# Design detail
+
+Go into detail on the design of the API, This is where you go past the surface and explain the mechanics of how the API works. If a step-by-step direction is possible, provide it.
+
+# Open questions
+
+The first draft of any proposal is not going to have all of the answers. Take this space to be clear of what is still unknown.
+
+# Previous considerations
+
+List any previous proposals or priority art that inspired this proposal.