famapp/docs/tasks

Task briefs

Each file here is a self-contained brief for a sub-session (typically Sonnet) to execute one chunk of work. Briefs assume the executor has read /CLAUDE.md — do not restate the stack or architecture there.

How to use a brief

1. Read /CLAUDE.md first.
2. Read the task file end-to-end.
3. Stop when all acceptance criteria pass. Do not bolt on extra scope.
4. If a brief turns out to be wrong, update the brief in the same commit as the code.

Brief format

Every task file has these sections:

• Goal — one sentence.
• Why — what this unlocks; how it fits the larger plan.
• Depends on — task numbers that must be done first.
• Scope — bullet list of what to build.
• Out of scope — explicit non-goals to prevent drift.
• Acceptance criteria — checkable list. Done = all checked.
• Notes — gotchas, recommended libs, sketches.

Phase index

Phase 1 — Scaffold

• 01 — Repo init & tooling
• 02 — Next.js app skeleton
• 03 — Drizzle + Postgres setup
• 04 — Module loader & registry
• 05 — Compose stack & Caddy
• 06 — Authentik install + OIDC integration
• 07 — Household seeding & session

Phase 2 — Core modules

• 10 — Calendar module
• 11 — Lists module (shopping + task)
• 12 — Notes module

Phase 3 — Dashboard & UX

• 20 — Dashboard composition
• 21 — Quick-add registry
• 22 — Activity log

Phase 4 — Sharing

• 30 — Share-link service
• 31 — Public share viewer (/s/<token>)

Phase 5 — Notifications & reminders

• 40 — Web Push (VAPID)
• 41 — Reminders engine
• 42 — Notification bus + ntfy adapter

Phase 6 — PWA polish

• 50 — Manifest, icons, install prompt
• 51 — Offline shell + service worker caching

Phase 7 — Hardening

• 60 — Postgres backups (pg_dump cron)
• 61 — Rate limiting on share links
• 62 — Structured logging