dev-swarm-stage-mvp

To define MVP scope, analyze existing project documentation and user needs to outline essential features, prioritize them using frameworks like MoSCoW, and establish measurable success criteria for delivering the smallest testable product.

Feature prioritization for release planning organizes features using frameworks like MoSCoW to categorize must-haves versus nice-to-haves, ensuring the initial launch focuses only on core features needed to validate assumptions and gather early user feedback.

MVP scope definition requires analysis of existing project documentation and user needs to formulate a focused roadmap. Without this prerequisite documentation, the skill cannot accurately establish the essential features or success criteria for product validation.

The best way to establish MVP success criteria is to analyze user needs and project documentation, then define measurable goals specifically designed to validate your core assumptions efficiently with the smallest testable product release.

You should not use an MVP approach when you lack existing project documentation or user needs data, as the scope definition process requires these inputs to formulate a focused roadmap and establish meaningful success criteria.