Feature Overview (aka. Goal Summary)

Feature to contain things like:

• support building parts of Backstage under a different scope (eg., forks of backstage/backstage components pushed to @red-hat-developer-hub scope)
• a migration tool for easier updates between releases
• what to do when issues like RHIDP-4116 / RHIDP-4117 happen and we can't just grab a BS 1.31 plugin into a 1.29-based RHDH without breaking changes

Goals (aka. expected user outcomes)

The observable functionality that the user now has as a result of receiving
this feature. Include the anticipated primary user type/persona and which
existing features, if any, will be expanded.

<your text here>

Requirements (aka. Acceptance Criteria):

A list of specific needs or objectives that a feature must deliver in order
to be considered complete. If the feature spans across releases then good
to have scope for each release with acceptance criteria. Be sure to
include nonfunctional requirements such as security, reliability,
performance, maintainability, scalability, usability, etc.

<enter general Feature acceptance here>

Out of Scope (Optional)

High-level list of items that are out of scope.

<your text here>

Customer Considerations (Optional)

Provide any additional customer-specific considerations that must be made
when designing and delivering the Feature. Initial completion during
Refinement status.

<your text here>

Documentation Considerations

Provide information that needs to be considered and planned so that
documentation will meet customer needs. If the feature extends existing
functionality, provide a link to its current documentation.

<your text here>