GitHub Roadmap Anchor Reuse Use when a user wants roadmap-level analysis, follow-on issue creation, or execution tracking for an area that already has a closed or stale roadmap/epic issue. Why Creating a fresh replacement epic is often the wrong default when a historical roadmap issue already exists. Reopening the original anchor preserves traceability, keeps prior discussion/context in one place, and avoids splitting execution across parallel umbrella issues. When to use Use this skill when: - You discover an older closed roadmap/epic issue for the same domain - You already created a new umb…