# Claude Code Task Briefs — Phase 1 Feature Build

These are tight, scoped briefs designed to be pasted into Claude Code on your
laptop. Each fits in a single Claude Code session (~30–60 min wall time).

## Recommended order

Build in this order — each task assumes the previous ones are done.

| # | Task | Est. Effort | Unblocks |
|---|---|---|---|
| 1 | [google-maps-integration](./01-google-maps-integration.md) | M | All location + distance flows |
| 2 | [location-autocomplete-component](./02-location-autocomplete-component.md) | M | Vihar create form |
| 3 | [vihar-create-form](./03-vihar-create-form.md) | M | Vihar lifecycle |
| 4 | [vihar-allocate-step](./04-vihar-allocate-step.md) | M | WhatsApp share |
| 5 | [vihar-share-sheet](./05-vihar-share-sheet.md) | S | End-to-end captain flow |
| 6 | [vihar-list](./06-vihar-list.md) | S | Captain visibility |
| 7 | [vihar-detail-captain](./07-vihar-detail-captain.md) | M | Reassign, manual close |
| 8 | [vihar-detail-volunteer](./08-vihar-detail-volunteer.md) | M | Volunteer flow |
| 9 | [volunteer-checkin](./09-volunteer-checkin.md) | S | Check-in |
| 10 | [volunteer-checkout](./10-volunteer-checkout.md) | M | Check-out + tolerance |
| 11 | [volunteer-master](./11-volunteer-master.md) | M | Add volunteers |
| 12 | [stats-aggregations](./12-stats-aggregations.md) | M | Real dashboards |
| 13 | [captain-dashboard-charts](./13-captain-dashboard-charts.md) | M | Visual stats |
| 14 | [volunteer-history-stats-leaderboard](./14-volunteer-history-stats-leaderboard.md) | S | Volunteer pages |
| 15 | [profile-change-password](./15-profile-change-password.md) | S | Password change |

## How to use a brief

1. On your laptop: `cd ~/projects/vihar-sewa`
2. Open Claude Code: `claude`
3. Tell it: "Read `docs/tasks/03-vihar-create-form.md` and implement it. Run the dev servers with `pnpm dev` to test as you go."
4. Claude Code will read the brief, ask clarifying questions if needed, and write the code.
5. After it's done: review the diff, run the smoke test from the Acceptance section, commit.

## Conventions every brief follows

- **File paths** are relative to repo root.
- **Acceptance** is the smoke test — if those steps pass, the task is done.
- **Gotchas** are bugs Claude Code is likely to introduce; flag them up front.
- **Out of scope** lists what NOT to do — keeps the task tight.

## When something doesn't fit a brief

If a task feels too big or you hit blockers Claude Code can't resolve, come
back to the chat with: the brief name, the failing step, and the error message.
I'll either patch the brief or unblock the issue.
