plan-roadmap

To turn early-stage product ideas into a structured roadmap, use a two-phase workflow that formalizes initial discussions into a prioritized sequence of implementation steps. It generates a draft Roadmap.md and a discussion-summary.md without producing implementation code.

The best way to plan features without writing implementation code is to use a workflow that generates only planning documents, metadata, and placeholders. It produces a PR-ready Roadmap.md and discussion summaries in a temporary draft area before moving them to your main repository.

Yes, you can use the feature planning process to capture goals and acceptance criteria before development. Phase 1 uses an interactive conversation to surface constraints and goals, which are then transformed into a structured roadmap with defined steps in Phase 2.

Roadmap planning does not generate files directly in the main GitHub repository initially. All outputs, including the Roadmap.md and lifecycle state markers, are written to a temporary draft directory and moved to the main repo by an activation step.

The feature roadmap planning workflow produces a Roadmap.md containing prioritized implementation steps, a discussion-summary.md capturing the initial conversation, and lifecycle state markers. These documents are created without generating any implementation code.

You should avoid using a structured roadmap planning process if your project requires immediate implementation code rather than planning documents. This workflow specifically generates metadata, roadmaps, and placeholders, ensuring no implementation code is produced during the planning phase.