Roadmap Anchor Issue Governance Use when a repo already has old roadmap/epic issues and you need to add a new analysis or execution wave without creating issue sprawl. When to use - A prior roadmap/umbrella issue exists but is closed or stale - New work is partly continuation of old roadmap logic and partly new scoped tasks - You need to balance reopen/retarget vs creating fresh issues - The user cares about work quality, traceability, and avoiding duplicate issue trees Core rule Prefer this structure: 1. Reopen the original roadmap/umbrella issue if it still cleanly owns the domain 2. Keep e…