roadmap

## Purpose Review your product roadmap holistically - surface blockers, identify stale initiatives, and ensure alignment with strategic priorities. This gives you a quick health check of all roadmap work. ## Usage - `/roadmap` - Full roadmap review - `/roadmap [pillar-name]` - Filter by specific pillar --- ## Step 1: Gather Roadmap Context Read roadmap-related projects and context: 1. **Scan 04-Projects/** for project files 2. **Read System/pillars.yaml** for strategic pillars 3. **Read 01-Quarter_Goals/Quarter_Goals.md** (if quarterly planning enabled) 4. **Search for roadmap mentions** in recent meeting notes (last 30 days) --- ## Step 2: Analyze Projects For each project in 04-Projects/, extract: **Status indicators:** - Last modified date (flag if > 14 days without update) - Completion status (in progress, blocked, completed) - Pillar tags (ensure they exist and are valid) **Blockers:** - Search for keywords: "blocked", "waiting", "dependency", "need" - Extract stakeholder dependencies - Identify missing decisions **Alignment:** - Check if project tags match pillars in System/pillars.yaml - Verify project supports a quarterly goal (if applicable) - Note projects without clear pillar alignment --- ## Step 3: Check Recent Feedback Search recent meeting notes (00-Inbox/Meetings/ from last 30 days) for: - Customer feedback on roadmap items - Stakeholder concerns about priorities - Competitive mentions that might affect roadmap - Requests for roadmap changes o...