Feature Scope Definition
Definition
Set the boundaries for one feature. Scope protects design quality by naming what will be built now, what is deferred, and what would create unnecessary complexity.
Questions To Ask
- What user behavior is included in this feature?
- What frontend, API, backend, data, and test work is required?
- What is explicitly excluded or deferred?
- What dependencies or prior slices are required?
- What would make this feature too large?
Existing Project Comparison
- Compare scope against current modules, routes, schemas, components, tests, and feature docs.
- Identify hidden dependencies, unrelated refactors, and old behavior that must be preserved.
- Flag scope that duplicates another feature or crosses ownership boundaries without reason.
Suggestive Plan
- Define included behavior.
- Define excluded behavior.
- List affected layers.
- List dependencies and assumptions.
- Split the feature if it cannot be tested as one vertical slice.
Example
Included: edit preferred time window for pending requests. Excluded: editing confirmed appointments, calendar sync, audit export, bulk editing.
Vocabulary
- Feature scope: the boundary of work for one feature.
- Deferred work: known work intentionally left for later.
- Affected layer: frontend, API, backend, database, or test surface touched by the feature.
- Vertical slice: smallest end-to-end feature increment.
Expected Outcome
Produce a scope contract with included behavior, excluded behavior, dependencies, affected layers, and split recommendations.
1---2name: feature-scope-definition3description: Define or audit the exact scope of one feature, including included behavior, excluded behavior, dependencies, and layer impact. Use before designing or implementing a feature to keep the slice small and strategic.4---56# Feature Scope Definition78## Definition910Set the boundaries for one feature. Scope protects design quality by naming what will be built now, what is deferred, and what would create unnecessary complexity.1112## Questions To Ask1314- What user behavior is included in this feature?15- What frontend, API, backend, data, and test work is required?16- What is explicitly excluded or deferred?17- What dependencies or prior slices are required?18- What would make this feature too large?1920## Existing Project Comparison2122- Compare scope against current modules, routes, schemas, components, tests, and feature docs.23- Identify hidden dependencies, unrelated refactors, and old behavior that must be preserved.24- Flag scope that duplicates another feature or crosses ownership boundaries without reason.2526## Suggestive Plan27281. Define included behavior.292. Define excluded behavior.303. List affected layers.314. List dependencies and assumptions.325. Split the feature if it cannot be tested as one vertical slice.3334## Example3536Included: edit preferred time window for pending requests. Excluded: editing confirmed appointments, calendar sync, audit export, bulk editing.3738## Vocabulary3940- Feature scope: the boundary of work for one feature.41- Deferred work: known work intentionally left for later.42- Affected layer: frontend, API, backend, database, or test surface touched by the feature.43- Vertical slice: smallest end-to-end feature increment.4445## Expected Outcome4647Produce a scope contract with included behavior, excluded behavior, dependencies, affected layers, and split recommendations.
harsh817