phase-plan

To convert architecture documentation into an actionable roadmap, the system extracts architecture-driven phases and generates an epic registry. It maps features to packages and cross-phase dependencies, outputting structured roadmap artifacts for project planning.

Mapping project epics to architecture phases involves enumerating phases and associating features to cross-phase dependencies. This produces a dependency graph and per-epic documentation, ensuring outputs align with the phase plan structure and update project context.

Yes, you can generate a dependency graph directly from architecture docs. The process reads the architecture document, identifies dependencies across phases, and produces a dependency graph markdown file alongside an organized epic registry.

Creating per-epic documentation artifacts involves deriving epics from the architecture document and generating individual files for each epic. These artifacts are stored under the docs/roadmap directory to maintain the project context and roadmap structure.

Extracting epics from an architecture document generates specific output files including a JSON epic registry, a markdown dependency graph, and per-epic documentation artifacts. These are saved in the docs/roadmap directory and update the project context.

You need a completed architecture document to generate an epic registry and roadmap. The process relies on reading existing architecture documentation to extract phases, identify dependencies, and produce actionable project planning artifacts.