x-internal-map-epic

To generate an implementation map, provide the file path to your epic. The skill reads epic and story metadata, derives dependency chains, and outputs an IMPLEMENTATION-MAP.md containing phase diagrams and lifecycle planning columns.

Critical path analysis for story dependencies works by assembling a dependency DAG from epic and story files, computing parallel work phases, and identifying bottlenecks. It then visualizes the critical path using ASCII diagrams and Mermaid graphs for planning visibility.

Yes, you can use Mermaid graphs to visualize story dependencies. The skill computes phases from your epic metadata to reveal parallel work streams and generates Mermaid graph outputs alongside ASCII diagrams within the implementation map.

The best way to identify bottlenecks in an epic implementation plan is to derive the dependency chains and critical path from your stories. The skill analyzes these dependencies to highlight bottlenecks and outputs the results in an IMPLEMENTATION-MAP.md file.

Yes, you need specific metadata in your epic and story files to calculate the implementation plan. The skill reads this metadata to verify dependencies, assemble a dependency DAG, and accurately compute the critical path and parallel work phases.

You need an ASCII phase diagram for epic planning when you require lightweight, text-based visibility into parallel work streams and story dependencies. The skill produces these diagrams within the IMPLEMENTATION-MAP.md to guide planning workflows without external rendering tools.