Feature Overview (aka. Goal Summary): <An elevator pitch (value statement) that describes the Feature in a clear and concise way.>

Goals (aka. expected user outcomes):
<The observable functionality that the user now has as a result of receiving this feature.>

Requirements (aka. Acceptance Criteria):
<A list of specific needs or objectives that a feature must deliver in order to be considered complete. Be sure to include nonfunctional requirements such as security, reliability, performance, maintainability, scalability, usability, etc.>

(Optional) Use Cases:
<Include use case diagrams, main success scenarios, alternative flow scenarios>

Questions to Answer:
<Include a list of questions that may need to be answered before coding can begin.>

Out of Scope
<High-level list of items that are out of scope>

Background
<Provide any additional context is needed to frame the feature.>

Customer Considerations
<Provide any additional customer-specific considerations that must be made when designing and delivering the Feature.>

Documentation Considerations
<Provide information that needs to be considered and planned so that documentation will meet customer needs.>