Slicing Product Scope

Goal

Separate the approved direction into coherent product outcomes that a developer can understand and later translate into engineering work.

Preconditions

• Read the full canonical brief.
• Status is product-design-approved.
• Product behavior is approved.

Hard boundary

PRODUCT SLICES ARE NOT ENGINEERING TASKS.

Do not list files, functions, endpoints, database changes, classes, migrations, test suites, commits, or implementation sequence. Those belong to technical brainstorming and implementation planning.