roadmap-integration

Validate new product features against your project vision by checking them against docs/project/overview.md. This ensures proposed backlog items align with core objectives before prioritization, preventing scope drift in your roadmap.

Automate GitHub issue creation for your roadmap by using the /roadmap command. This generates issues with YAML frontmatter containing area, role, slug, and alignment notes, while auto-applying labels for quick categorization.

Creation-order prioritization for backlog items works by sequencing work items into a backlog → next → in-progress workflow. This approach ensures older feature requests are addressed first, maintaining a structured roadmap progression.

You need a project overview file at docs/project/overview.md to align your roadmap. When present, the system validates new features against it; without this file, vision-alignment checks cannot be performed during feature creation.

The best way to prevent scope drift when adding features is enforcing vision validation and YAML frontmatter standardization. This ensures every backlog item is checked against your project overview and properly categorized before work begins.

Roadmap features may be missing alignment notes in GitHub issues if the project overview file is absent or if features are added outside the /roadmap command. This command guarantees YAML frontmatter and alignment notes are generated.