maintain-project-roadmap

To validate a ROADMAP.md file against a strict schema, run a check-only audit on your project root to enforce required sections, ordered milestones, and allowed status values without modifying unrelated files.

Migrating a legacy table-style roadmap to a checklist format involves applying bounded updates that transform outdated structures into a canonical schema. This process generates missing ROADMAP.md files from templates and enforces section ordering deterministically.

Generating a table of contents for your project roadmap is handled through bounded apply mode, which applies deterministic, minimal edits to fix structural issues while maintaining milestone integrity.

You can customize roadmap validation by applying project-specific configuration overrides for section ordering, additional sections, and status vocabularies. This allows the canonical checklist schema to adapt to your project's specific milestone tracking requirements.

Roadmap validation requires the pyyaml dependency to parse configuration files and apply schema rules. It operates directly on your project root directory to audit the ROADMAP.md file without touching unrelated files.

The limitation of bounded apply mode for roadmap maintenance is that it only applies deterministic, minimal edits to fix structural schema issues. It does not modify unrelated files or handle content semantics outside the defined checklist schema boundaries.