harness-roadmap

To generate a unified project roadmap, you can discover specs and plans to group features into milestones and write a compliant docs/roadmap.md file. This process requires human confirmation before writing to ensure an authoritative structure.

Roadmap synchronization works by mapping plans and linking specs to keep statuses updated with artifact state. This automated tracking reduces manual drift and rework when maintaining the docs/roadmap.md file.

Yes, you can use MCP tooling to manage project roadmaps by creating, updating, syncing, and querying milestones. It provides interactive workflows with guardrails and validation for direct markdown edits.

The best way to structure a docs/roadmap.md file is to group features into milestones and link docs/changes/*/proposal.md files. This creates a coherent, human-approved roadmap that stays compliant with project governance.

Yes, you need human approval to update the project roadmap because the workflow enforces human-confirmed changes. Bootstrapping the roadmap also requires explicit confirmation before writing the docs/roadmap.md file.

Your project roadmap drifts when manual updates fail to keep statuses in sync with artifact state. Automating the discovery of specs and plans enforces a unified structure that reduces this drift and rework.