docs(02): create phase plan — 5 plans in 4 waves covering rooms, tasks, templates, and verification

.planning/ROADMAP.md

@@ -45,7 +45,13 @@ Plans:
   4. User can mark a task done (tap or swipe), which records the completion and sets the next due date correctly based on the interval
   5. Overdue tasks are visually highlighted with a distinct color or badge on room cards and in task lists; tasks within a room are sorted by due date by default
   6. Each room card shows its name, icon, count of due tasks, and cleanliness indicator
-**Plans**: TBD
+**Plans**: 5 plans
+Plans:
+- [ ] 02-01-PLAN.md — Data layer: Drift tables, migration v1->v2, DAOs, scheduling utility, domain models, templates, tests
+- [ ] 02-02-PLAN.md — Room CRUD UI: 2-column card grid, room form, icon picker, drag-and-drop reorder, providers
+- [ ] 02-03-PLAN.md — Task CRUD UI: task list, task row with completion, task form, overdue highlighting, providers
+- [ ] 02-04-PLAN.md — Template selection: template picker bottom sheet, room type detection, integration with room creation
+- [ ] 02-05-PLAN.md — Visual and functional verification checkpoint
 
 ### Phase 3: Daily Plan and Cleanliness
 **Goal**: Users can open the app and immediately see what needs doing today, act on tasks directly from the plan view, and see a room-level health indicator
@@ -81,6 +87,6 @@ Note: Phase 4 depends on Phase 2 (needs scheduling data) but can be developed in
 | Phase | Plans Complete | Status | Completed |
 |-------|----------------|--------|-----------|
 | 1. Foundation | 2/2 | Complete    | 2026-03-15 |
-| 2. Rooms and Tasks | 0/TBD | Not started | - |
+| 2. Rooms and Tasks | 0/5 | Planning complete | - |
 | 3. Daily Plan and Cleanliness | 0/TBD | Not started | - |
 | 4. Notifications | 0/TBD | Not started | - |