<!-- SPDX-FileCopyrightText: 2026 FocusFlow contributors -->
<!-- SPDX-License-Identifier: AGPL-3.0-only -->

# UI Plan 2 — Execution Order

Follow this order exactly. Stop at each `BREAKPOINT` if Codex is operating in an interactive repo session.

1. `UI_PLAN_2_BLOCK_01_REPO_SCOPE_AND_ASSETS.md`
2. `UI_PLAN_2_BLOCK_02_BACKLOG_READ_MODELS_AND_METADATA.md`
3. `UI_PLAN_2_BLOCK_03_NAVIGATION_AND_SCREEN_SHELL.md`
4. `UI_PLAN_2_BLOCK_04_BOARD_COLUMNS_AND_CARDS.md`
5. `UI_PLAN_2_BLOCK_05_SEARCH_FILTER_SORT_GROUP.md`
6. `UI_PLAN_2_BLOCK_06_SUMMARY_PANEL.md`
7. `UI_PLAN_2_BLOCK_07_TASK_DETAIL_DRAWER.md`
8. `UI_PLAN_2_BLOCK_08_COMMANDS_CREATE_AND_ACTIONS.md`
9. `UI_PLAN_2_BLOCK_09_TESTING_VALIDATION_HANDOFF.md`

Minimum validation after each block:

```sh
cd apps/focus_flow_flutter
flutter analyze
flutter test
```

Additional validation after blocks that touch packages:

```sh
dart analyze
dart test
```

Full project validation at the end, if available in the working environment:

```sh
scripts/test.sh
```

Commit guidance:

- Commit after each completed block.
- Use conventional commit style.
- Example block commits:
  - `feat(backlog): add board read models`
  - `feat(ui): add backlog navigation shell`
  - `feat(ui): render backlog board cards`
  - `feat(ui): add backlog detail drawer`
  - `test(ui): cover backlog board interactions`
