ferrox-mvp-phase

To convert a project phase into an MVP slice, validate the phase goal using user-story framing and apply SPIDR scope splitting to define a thin end-to-end increment before updating the roadmap.

SPIDR scope splitting is a technique evaluating whether a user story is too large, offering structured division across Spike, Paths, Interfaces, Data, and Rules to maintain a thin MVP increment.

Write a user story for MVP phase planning by defining the goal using an "As a / I want to / So that" statement, ensuring the phase scope remains thin and shippable before roadmap delegation.

MVP phase planning requires an existing project roadmap because it performs phase existence checks and writes MVP mode directly into the phase roadmap before delegating to downstream planning.

The best way to prevent oversized scope is enforcing user-story validation and applying SPIDR scope splitting to break down large stories into thin, end-to-end MVP increments before execution.

MVP phase planning delegates to a downstream planning workflow to hand off the validated MVP slice, ensuring the roadmap is updated with MVP detection before execution begins.