gsd-mvp-phase

SPIDR splitting in MVP planning assesses complex user stories using specific criteria to break them down, ensuring a focused and manageable Minimum Viable Product phase for project managers and software developers.

Plan an MVP phase by guiding structured user story development and SPIDR-based splitting to define scope, followed by inserting finalized MVP planning information directly into your project roadmap document.

Split user stories for roadmap creation when they are too complex for a single MVP phase. SPIDR criteria assess these stories and suggest breaking them down to maintain a manageable and focused roadmap.

Yes, you can use this MVP planning approach without dependencies. It operates independently to facilitate user story development, apply SPIDR splitting, and update the roadmap document within a structured project management context.

MVP mode auto-detection identifies the active MVP planning context and automatically directs the workflow to the next appropriate step, streamlining the transition between user story development and roadmap updates.

Start MVP phase planning by activating the planning skill with a specific phase number argument, which initiates structured user story development and SPIDR-based splitting for that targeted phase.