workflow-planning-03-write-development-phases

To generate a phased product roadmap, place your existing PRD.md and Marketresearch.md in the repository. The workflow analyzes these documents to synthesize insights and outputs a structured plan mapping features, dependencies, and timelines to .agents/product/ProductPhases.md.

Defining MVP scope and growth phases is best handled by synthesizing existing product documentation into a structured timeline. This workflow reads your product artifacts to map MVP features, Phase 2 enhancements, and Phase 3 growth initiatives with clear goals and success criteria.

Yes, you can use PRD.md and Marketresearch.md files to plan development timelines. The workflow reads these saved source documents, analyzes dependencies, and produces a formal ProductPhases.md file outlining phase goals, timelines, and risk considerations.

Automated roadmap generation suits teams planning an MVP with a short runway, such as a three-month timeline. It converts scattered product artifacts into a comprehensive phased plan outlining MVP features and subsequent growth initiatives.

The output roadmap uses a markdown format and is saved directly to .agents/product/ProductPhases.md. This formal document includes clear phase goals, dependencies, timelines, and success criteria for your product launch.

You need a structured phased plan instead of a basic feature list when mapping dependencies and timelines across MVP and growth phases. This approach transforms scattered documentation into a formal roadmap with clear goals and risk considerations for product launches.