rnd-roadmappinglisted

# R&D Roadmapping ## Overview For work that spans multiple sessions, a roadmap tracks progress across pipeline runs. Each milestone is one session's worth of deliverable work. **Core principle:** Each milestone must be independently valuable. If you stop after M2, M1 and M2 should still be useful — not half-finished infrastructure. ## When to Use - Before starting multi-session work with a Planner - When updating milestone status after a SHIP verdict - When parking mid-session work and planning resumption ## roadmap.md Format ```markdown # Roadmap: [Broad Task Title] Created: YYYY-MM-DD Last updated: YYYY-MM-DD ## Goal [1-3 sentences describing the overall multi-day objective] ## Milestones ### M1: [Title] [STATUS] **Description:** [What this milestone delivers — 1-3 sentences, enough for a /start session] **Session:** [session ID, filled after milestone starts] **Delivered:** [Summary of what was built, filled after DONE] ### M2: [Title] [STATUS] **Description:** ... **Session:** ... **Delivered:** ... ``` ## Milestone Statuses Exactly four statuses: `NOT_STARTED`, `IN_PROGRESS`, `DONE`, `SKIPPED` - `NOT_STARTED` → `IN_PROGRESS`: a session starts for this milestone - `IN_PROGRESS` → `DONE`: SHIP verdict — record session ID + deliverables - `IN_PROGRESS` → `SKIPPED`: user decides to skip (record reason inline) - `NOT_STARTED` → `SKIPPED`: user decides to skip before starting ## Where roadmap.md Lives Store at the project base dir — output of `rnd-dir.sh --bas