stakeholder-roadmap-generator

To generate a stakeholder roadmap, the tool reads your capabilities.yaml and PRD.md to assemble a top-down ROADMAP.md with phase-based sections. It applies stable decimal IDs and topological ordering to produce a readable document for stakeholders.

Topological ordering is needed when your roadmap must reflect dependency chains across capabilities before presentation. It ensures the generated ROADMAP.md sequences phases correctly, preventing stakeholders from viewing disconnected or out-of-order product milestones.

Yes, you can regenerate the ROADMAP.md on-demand while preserving previous decimal IDs. This maintains stable contracts across regenerations, ensuring stakeholders reference consistent milestone identifiers even when capability inputs change.

Roadmap generation requires a capabilities.yaml and a PRD.md as authoritative inputs, while an optional ARCHITECTURE.md provides supplementary context. These files assemble the top-down roadmap and render a footer reflecting the tech stack and dependencies.

This approach works for any product that maintains a capabilities.yaml and PRD.md in its planning directory. It is tech-stack agnostic, rendering the ROADMAP.md footer to reflect specific dependencies dynamically based on the provided inputs.

Roadmap milestone IDs typically shift when updates lack a stable decimal-id enforcement mechanism. This generator applies stable decimal IDs and topological ordering during regeneration, preserving previous identifiers to maintain stakeholder contracts.