Skip to content

TASK_BREAKDOWN.md

Latest commit

 

History

History
204 lines (151 loc) · 47.9 KB

TASK_BREAKDOWN.md

File metadata and controls

204 lines (151 loc) · 47.9 KB
Raw

Task Breakdown

Version: 0.1.0
Date: 2026-05-23
Author: Claude Code
Status: Draft
Phase: Sprint Planning

How to Use

This board splits the documented user stories and acceptance criteria into shippable engineering cards. Each card has one owner, cites real AC IDs from docs/business/, and points to the technical source of truth that constrains the work.

Engineer Composition

Placeholder Role
BE1 Backend Engineer
FE1 Frontend Engineer
TL Tech Lead

Work Model

  • Cards are sized around 2 to 3 developer-days.
  • Tech Lead cards establish API specifications before backend implementation for endpoint-backed features.
  • Backend cards implement persistence, domain engines, server actions, and route handlers against approved contracts.
  • Frontend cards own user-facing routes, components, loading states, error states, and visual polish.
  • TL cards own scaffold, guardrails, cross-cutting verification, seeds, and release-quality checks.
  • Wiring cards are explicit when backend and frontend work must be proven end-to-end against the running app.
  • US-21 implementation remains optional follow-up for Sprint 5, but its recovery contracts are captured in the API-spec card so the scope is explicit.

Sprint 1: Establish production foundation: full data model, username/password auth, sessions, persistence, user-local days, audit/retention model, and core scoring

Stories: US-02, US-06, US-07, US-08, US-16, US-19, US-22
Goal: Establish persistent account, session, event, snapshot, audit, timezone, and scoring foundations that later product sprints can build on.

Tech Lead

Card ID PM Card Title Task Description AC Owner Est Docs
TL-S1-01 Specify foundation API and action contracts Create docs/api-specs/foundation-contracts.md covering auth actions, session shape, private route access behavior, activity submission, daily snapshot reads, scoring reads, audit logging expectations, timezone handling, and health/reset contracts before BE-S1-02 through BE-S1-06 implement them. AC-02.01, AC-02.02, AC-02.03, AC-02.05, AC-02.06, AC-02.07, AC-02.08, AC-02.09, AC-02.10, AC-02.11, AC-02.12, AC-02.13, AC-02.14, AC-02.15, AC-02.16, AC-02.17, AC-06.01, AC-06.02, AC-06.03, AC-06.04, AC-06.05, AC-06.06, AC-06.07, AC-06.08, AC-06.09, AC-06.10, AC-06.11, AC-06.12, AC-07.01, AC-07.02, AC-07.03, AC-07.04, AC-07.05, AC-07.06, AC-07.07, AC-07.08, AC-07.09, AC-08.01, AC-08.02, AC-08.03, AC-08.04, AC-08.05, AC-08.06, AC-08.07, AC-08.08, AC-08.09, AC-08.10, AC-08.11, AC-08.12, AC-08.13, AC-08.14, AC-16.01, AC-16.02, AC-16.03, AC-16.04, AC-16.05, AC-16.06, AC-16.07, AC-16.08, AC-16.09, AC-19.01, AC-19.02, AC-19.03, AC-19.04, AC-19.05, AC-22.01 TL 2 03-repository-structure.md §docs/api-specs, 05-module-definitions.md, 10-integration-points.md

Backend

Card ID PM Card Title Task Description AC Owner Est Docs
BE-S1-01 Implement database schema and migrations Create Drizzle schema, migrations, repositories, and seed boundaries for users, sessions, activity events, daily snapshots, inventory, quests, demo states, share snapshots, token placeholders, and audit events. AC-02.05, AC-16.01, AC-16.02, AC-16.03, AC-16.04, AC-16.05, AC-16.06, AC-16.07, AC-16.09, AC-19.01, AC-19.08, AC-22.01 BE1 3 06-data-model.md §6.1-6.15, 05-module-definitions.md §5.10
BE-S1-02 Build username password auth services Implement registration, login, password hashing, username normalization, reserved names, password policy, optional email, JWT-backed session creation, and audit events. AC-02.01, AC-02.02, AC-02.03, AC-02.04, AC-02.10, AC-02.11, AC-02.12, AC-02.13, AC-02.14, AC-02.15, AC-02.16, AC-02.17, AC-19.07 BE1 3 09-authentication-and-authorization.md §9.1-9.3, 05-module-definitions.md §5.2
BE-S1-03 Enforce private route authorization Add requireUser, requireSuperadmin, owner-scoped repository access, protected-route helpers, and RBAC tests proving account isolation. AC-02.06, AC-02.07, AC-02.08, AC-02.09, AC-19.03, AC-19.04 BE1 2 09-authentication-and-authorization.md §9.4-9.5, 10-integration-points.md §10.4
BE-S1-04 Implement activity ingestion and daily energy Add normalized activity recording with idempotency, source handling, action caps, daily target calculations, and user-local day reset behavior. AC-06.01, AC-06.02, AC-06.03, AC-06.04, AC-06.05, AC-06.06, AC-06.08, AC-06.09, AC-06.10, AC-06.11, AC-06.12, AC-19.06, AC-22.01 BE1 3 05-module-definitions.md §5.4, 13-scoring-game-loop-strategy.md §13.1-13.6
BE-S1-05 Implement health and seniority scoring Add pure scoring functions for health, missed-day processing, seniority score, weighted breakdown, deep tag recognition, tag normalization, and snapshot persistence. AC-07.01, AC-07.02, AC-07.03, AC-07.04, AC-07.05, AC-07.06, AC-07.07, AC-07.08, AC-08.01, AC-08.02, AC-08.03, AC-08.04, AC-08.05, AC-08.06, AC-08.07, AC-08.08, AC-08.09, AC-08.10, AC-08.11, AC-08.12, AC-08.13, AC-08.14, AC-16.02 BE1 3 13-scoring-game-loop-strategy.md §13.1-13.8, 06-data-model.md §6.7
BE-S1-06 Wire auth and scoring into protected flows Depends on BE-S1-02, BE-S1-03, FE-S1-01, and FE-S1-02; FE-S1-02 lands last, so FE owns final UI verification, while BE owns server-side route and action contract stabilization. AC-02.01, AC-02.02, AC-02.06, AC-02.08, AC-06.07, AC-07.09, AC-19.05 BE1 2 02-system-architecture.md §2.4-2.7, 05-module-definitions.md §5.1-5.5

Frontend

Card ID PM Card Title Task Description AC Owner Est Docs
FE-S1-01 Build registration and login screens Create account creation and login UI with validation messages, optional email handling, duplicate username feedback, password policy guidance, and session success navigation. AC-02.01, AC-02.02, AC-02.10, AC-02.11, AC-02.12, AC-02.13, AC-02.17 FE1 3 05-module-definitions.md §5.1, 09-authentication-and-authorization.md §9.2
FE-S1-02 Build protected shell and settings foundation Create dashboard and settings shells with protected-route behavior, unauthenticated prompts or redirects, public share exception placeholder, component-level error states, timezone capture, and daily target display. AC-02.06, AC-02.07, AC-02.08, AC-06.07, AC-16.07, AC-19.05, AC-22.01 FE1 3 05-module-definitions.md §5.1, 10-integration-points.md §10.4
FE-S1-03 Build foundation verification UI wiring Depends on BE-S1-06 and FE-S1-02; FE-S1-02 lands last, so FE owns the wiring. Verify account creation, login, private-route redirect, daily target display, and first snapshot rendering end-to-end against the running app. AC-02.01, AC-02.02, AC-02.06, AC-02.08, AC-06.07, AC-07.09, AC-19.05 FE1 2 02-system-architecture.md §2.4, 05-module-definitions.md §5.1

Sprint 2: Build landing, dashboard companion experience, server-persisted demo mode, prepared judge demo accounts, and minimal static share slice

Stories: US-01, US-04, US-05, US-12, US-13, US-18, US-20, US-14
Goal: Deliver the hackathon-facing product experience with landing, rubber duck dashboard, demo state, judge accounts, recent activity, and a minimal public share path.

Tech Lead

Card ID PM Card Title Task Description AC Owner Est Docs
TL-S2-01 Specify demo and share API contracts Create docs/api-specs/demo-share-contracts.md covering landing telemetry if any, demo state mutation, judge demo reset, dashboard companion reads, recent activity reads, and minimal share snapshot create/read routes before BE-S2-01 through BE-S2-05 implement them. AC-01.01, AC-01.02, AC-01.03, AC-04.01, AC-04.02, AC-04.03, AC-04.04, AC-04.05, AC-04.06, AC-05.01, AC-05.02, AC-05.03, AC-05.04, AC-12.01, AC-12.02, AC-12.03, AC-13.01, AC-13.02, AC-13.03, AC-13.04, AC-18.01, AC-18.02, AC-18.03, AC-18.04, AC-18.05, AC-20.01, AC-20.02, AC-14.01, AC-14.02, AC-14.03, AC-14.04, AC-14.05, AC-14.10 TL 2 05-module-definitions.md §5.11, 10-integration-points.md, 14-share-snapshot-privacy-strategy.md

Backend

Card ID PM Card Title Task Description AC Owner Est Docs
BE-S2-01 Implement server-persisted demo mode Add demo persona state, demo reset, simulation action application, API-independent behavior, and persistence across sessions for authenticated users. AC-04.01, AC-04.02, AC-04.03, AC-04.04, AC-04.05, AC-04.06, AC-04.07, AC-16.05 BE1 3 05-module-definitions.md §5.9, 06-data-model.md §6.12, 13-scoring-game-loop-strategy.md §13.2
BE-S2-02 Add judge account seed and reset operations Create controlled seed and reset operations for prepared judge demo accounts with audit events and deterministic demo state. AC-18.06, AC-20.01, AC-20.02, AC-19.07 BE1 2 05-module-definitions.md §5.12, 09-authentication-and-authorization.md §9.4-9.5, 06-data-model.md §6.15
BE-S2-03 Expose dashboard activity and companion view model Build the server model that returns pet hero state, speech inputs, stats, recent activity, onboarding flags, and demo controls without leaking private fields. AC-05.01, AC-05.03, AC-12.01, AC-12.02, AC-12.03, AC-13.02, AC-19.04 BE1 3 02-system-architecture.md §2.4, 05-module-definitions.md §5.1, §5.4, §5.8
BE-S2-04 Implement minimal share snapshot API Add static share snapshot creation, public lookup, safe field projection, public unauthenticated route data, and minimal Sprint 2 share slice behavior. AC-14.01, AC-14.02, AC-14.03, AC-14.04, AC-14.05, AC-14.10, AC-19.04 BE1 3 14-share-snapshot-privacy-strategy.md §14.1-14.7, 05-module-definitions.md §5.11
BE-S2-05 Record demo completion analytics Persist one demo_completed event only after the documented demo milestones are reached. AC-18.07, AC-19.07 BE1 2 06-data-model.md §6.13, 05-module-definitions.md §5.9

Frontend

Card ID PM Card Title Task Description AC Owner Est Docs
FE-S2-01 Build landing page hook and CTA Create the marketing page above-the-fold experience with product name, tagline, emotional subheadline, primary CTA, and focused narrative scope. AC-01.01, AC-01.02, AC-01.03 FE1 2 05-module-definitions.md §5.1, 01-overview.md
FE-S2-02 Build rubber duck dashboard hero Render the pet hero, dominant duck companion, speech bubble, core stats, onboarding, demo controls, future module states, and elegant dark developer interface. AC-05.01, AC-05.02, AC-05.03, AC-05.04, AC-13.05 FE1 3 05-module-definitions.md §5.1, 05-module-definitions.md §5.8
FE-S2-03 Add duck variants and micro-animations Create SVG or React duck variants, deterministic speech display, playful satire copy boundaries, one polished idle animation, and state-specific visual treatments. AC-13.01, AC-13.02, AC-13.03, AC-13.04, AC-13.05 FE1 3 05-module-definitions.md §5.1, §5.8, 13-scoring-game-loop-strategy.md §13.1
FE-S2-04 Render recent counted activity Add activity list UI with action type, post title, tags, energy earned, source, timestamp, and graceful handling of unavailable API fields. AC-12.01, AC-12.02, AC-12.03 FE1 2 05-module-definitions.md §5.1, §5.4, 10-integration-points.md §10.1
FE-S2-05 Build minimal public share experience Add create-share CTA, public share page, static snapshot rendering, privacy-safe field display, and public preview path for the judge demo. AC-14.01, AC-14.02, AC-14.03, AC-14.04, AC-14.05, AC-14.10, AC-18.04 FE1 3 14-share-snapshot-privacy-strategy.md §14.1-14.7, 05-module-definitions.md §5.11
FE-S2-06 Wire 60-second judge demo flow Depends on BE-S2-01 through BE-S2-05 and FE-S2-01 through FE-S2-05; FE-S2-05 lands last, so FE owns the wiring. Verify landing, login, demo mode entry, simulation action, energy or health change, quest placeholder progress, and share creation or preview in 60 seconds. AC-18.01, AC-18.02, AC-18.03, AC-18.04, AC-18.05, AC-18.06, AC-18.07 FE1 3 02-system-architecture.md §2.4, 05-module-definitions.md §5.1, §5.9, §5.11

Sprint 3: Add quests, power-ups, next best action, anti-doomscrolling, and recent activity explainability

Stories: US-09, US-10, US-11
Goal: Add game-loop depth through quests, rewards, inventory, next best action, and anti-doomscrolling guidance.

Tech Lead

Card ID PM Card Title Task Description AC Owner Est Docs
TL-S3-01 Specify quest and nudge API contracts Create docs/api-specs/quest-nudge-contracts.md covering quest generation reads, quest completion, inventory reads, power-up usage, next best action responses, anti-doomscrolling nudges, and activity explainability before BE-S3-01 through BE-S3-04 implement them. AC-09.01, AC-09.02, AC-09.03, AC-09.04, AC-09.05, AC-10.01, AC-10.02, AC-10.03, AC-10.04, AC-10.05, AC-11.01, AC-11.02, AC-11.03, AC-11.04, AC-11.05 TL 1 05-module-definitions.md, 13-scoring-game-loop-strategy.md

Backend

Card ID PM Card Title Task Description AC Owner Est Docs
BE-S3-01 Implement quest engine and persistence Add daily, personalized, and weekly quest definitions, progress calculation, reset cadence, persistence for progress and completion, and reward configuration. AC-09.01, AC-09.02, AC-09.03, AC-09.04, AC-09.05, AC-09.06, AC-16.04 BE1 3 05-module-definitions.md §5.6, 06-data-model.md §6.10, 13-scoring-game-loop-strategy.md §13.6
BE-S3-02 Implement power-up inventory and effects Add inventory mutation, max held quantities, one-shot effects, health and energy application, Revive Feather behavior, audit events, and seniority integrity tests. AC-10.01, AC-10.02, AC-10.03, AC-10.04, AC-10.05, AC-10.06, AC-10.07, AC-16.03, AC-19.06, AC-19.07 BE1 3 05-module-definitions.md §5.7, 06-data-model.md §6.8-6.9, 13-scoring-game-loop-strategy.md §13.5-13.6
BE-S3-03 Implement recommendation and nudge logic Add deterministic next best action selection from score, caps, tags, and recent events, with topic hints and fallback when only action type is known. AC-11.01, AC-11.02, AC-11.03, AC-11.04, AC-11.05 BE1 2 05-module-definitions.md §5.6, 13-scoring-game-loop-strategy.md §13.1-13.8

Frontend

Card ID PM Card Title Task Description AC Owner Est Docs
FE-S3-01 Build quest dashboard panel Render daily, personalized, and weekly quests with progress, completion state, reward copy, and reset cadence labels. AC-09.01, AC-09.02, AC-09.03, AC-09.04, AC-09.05, AC-09.06 FE1 3 05-module-definitions.md §5.1, §5.6, 13-scoring-game-loop-strategy.md §13.6
FE-S3-02 Build inventory and power-up controls Render earned power-ups, manual use controls, final-use feedback, max quantities, active effect messaging, and health recovery state. AC-10.01, AC-10.02, AC-10.03, AC-10.04, AC-10.05, AC-10.06, AC-10.07 FE1 3 05-module-definitions.md §5.1, §5.7, 13-scoring-game-loop-strategy.md §13.5
FE-S3-03 Build next best action and nudge UI Render the recommended action, topic hints when available, fallback copy, anti-doomscrolling guidance, and read-cap nudge states. AC-11.01, AC-11.02, AC-11.03, AC-11.04, AC-11.05 FE1 2 05-module-definitions.md §5.1, 13-scoring-game-loop-strategy.md §13.1
FE-S3-04 Wire quests, rewards, and nudges end-to-end Depends on BE-S3-01 through BE-S3-03 and FE-S3-01 through FE-S3-03; FE-S3-03 lands last, so FE owns the wiring. Verify normalized activity updates quest progress, grants inventory, allows manual use, and updates next best action without changing seniority directly. AC-09.04, AC-09.05, AC-10.01, AC-10.04, AC-10.05, AC-10.07, AC-11.01, AC-11.05 FE1 3 02-system-architecture.md §2.4, 13-scoring-game-loop-strategy.md §13.5-13.6

Sprint 4: Integrate daily.dev Public API with active token validation, token security, documented endpoints, pagination, rate limits, and fallbacks

Stories: US-03, US-15, US-17
Goal: Connect authenticated users to daily.dev safely while preserving demo reliability and documented fallback behavior.

Tech Lead

Card ID PM Card Title Task Description AC Owner Est Docs
TL-S4-01 Specify daily.dev integration contracts Create docs/api-specs/dailydev-integration-contracts.md covering token connect, token validation, token revocation, API fallback envelopes, rate-limit behavior, pagination cursors, profile/feed/bookmark/post/comment access, and demo fallback behavior before BE-S4-01 through BE-S4-05 implement them. AC-03.01, AC-03.02, AC-03.03, AC-03.04, AC-03.05, AC-03.06, AC-03.07, AC-03.08, AC-03.09, AC-15.01, AC-15.02, AC-15.03, AC-15.04, AC-15.05, AC-17.01, AC-17.02, AC-17.03, AC-17.04, AC-17.05, AC-17.06, AC-17.07, AC-17.08, AC-17.09 TL 2 12-dailydev-integration-strategy.md, 10-integration-points.md

Backend

Card ID PM Card Title Task Description AC Owner Est Docs
BE-S4-01 Implement token encryption and connection lifecycle Add authenticated token submission, server-side encryption, connection status, disconnect, revocation guidance support, and audit events without exposing tokens to the browser. AC-03.01, AC-03.03, AC-03.04, AC-03.08, AC-03.09, AC-19.04, AC-19.07 BE1 3 09-authentication-and-authorization.md §9.6, 12-dailydev-integration-strategy.md §12.1-12.6, 05-module-definitions.md §5.3
BE-S4-02 Implement active token validation Add GET /feeds/foryou validation, connected status only after success, friendly error categories, non-replacement of working connections, later invalid-token detection, and demo-mode fallback prompts. AC-03.02, AC-03.05, AC-03.06, AC-03.07, AC-03.10, AC-15.01 BE1 3 12-dailydev-integration-strategy.md §12.1-12.6, 10-integration-points.md §10.1
BE-S4-03 Implement daily.dev API client and mapping Add base URL client, bearer auth, feed, post, search, bookmark, profile, tech stack, cursor pagination, DTO mapping, and unsupported behavior fallback to Devine-tracked events. AC-17.01, AC-17.02, AC-17.03, AC-17.04, AC-17.05, AC-17.06, AC-17.07, AC-17.08, AC-17.09, AC-15.06 BE1 3 12-dailydev-integration-strategy.md §12.1-12.7, 10-integration-points.md §10.1
BE-S4-04 Add rate-limit and outage handling Implement recoverable 429 handling, retry-after interpretation, rate-limit header parsing, conservative retry behavior, timeout fallback, and server-wide token constraints for non-personal content only. AC-15.02, AC-15.03, AC-15.04, AC-15.05, AC-15.01 BE1 2 12-dailydev-integration-strategy.md §12.3-12.6, 10-integration-points.md §10.1

Frontend

Card ID PM Card Title Task Description AC Owner Est Docs
FE-S4-01 Build daily.dev settings connection UI Create token submission, Plus requirement copy, connected status, validation success and failure states, disconnect flow, revocation guidance, and demo fallback guidance. AC-03.01, AC-03.02, AC-03.06, AC-03.07, AC-03.08, AC-03.09, AC-03.10 FE1 3 05-module-definitions.md §5.1, 09-authentication-and-authorization.md §9.6, 12-dailydev-integration-strategy.md §12.2
FE-S4-02 Build connected-mode dashboard fallbacks Render recoverable API failure states, rate-limit states, missing history copy, personalized feed data where available, and demo-mode alternatives without crashing. AC-15.01, AC-15.03, AC-15.04, AC-15.06, AC-17.02, AC-17.08 FE1 3 10-integration-points.md §10.1, 12-dailydev-integration-strategy.md §12.4-12.6
FE-S4-03 Wire daily.dev connection end-to-end Depends on BE-S4-01 through BE-S4-04 and FE-S4-01 through FE-S4-02; FE-S4-02 lands last, so FE owns the wiring. Verify token validation, success status, failure copy, disconnect, rate-limit fallback, and connected dashboard data with no token exposure. AC-03.01, AC-03.04, AC-03.05, AC-03.06, AC-03.07, AC-03.08, AC-15.01, AC-15.03, AC-17.01, AC-17.09 FE1 3 02-system-architecture.md §2.4, 12-dailydev-integration-strategy.md §12.1-12.7

Sprint 5: Complete safe public share snapshots, soft deletion, GDPR retention cleanup, production polish, and final demo hardening

Stories: US-14, US-21
Goal: Finish privacy-safe share snapshot management, retention cleanup, and final demo hardening. US-21 implementation remains optional follow-up, with recovery contracts specified for scope control.

Tech Lead

Card ID PM Card Title Task Description AC Owner Est Docs
TL-S5-01 Specify recovery and retention contracts Create docs/api-specs/recovery-retention-contracts.md covering optional email recovery, share snapshot soft deletion, retention cleanup, privacy-safe public snapshot reads, and production hardening checks before BE-S5-01 through BE-S5-03 implement them. AC-14.06, AC-14.07, AC-14.08, AC-14.09, AC-14.10, AC-21.01, AC-21.02 TL 1 07-security.md, 08-non-functional-requirements.md, 14-share-snapshot-privacy-strategy.md

Backend

Card ID PM Card Title Task Description AC Owner Est Docs
BE-S5-01 Complete share snapshot soft deletion Add owner-only soft deletion, deleted public response behavior, HTTP 410 support, deletion audit events, and idempotent deletion semantics. AC-14.06, AC-14.07, AC-14.08, AC-19.06, AC-19.07 BE1 3 14-share-snapshot-privacy-strategy.md §14.1-14.7, 05-module-definitions.md §5.11
BE-S5-02 Implement share retention cleanup model Add retention metadata, cleanup query or script for soft-deleted snapshots, private event retention, token history retention, and audit record retention. AC-14.09, AC-19.08 BE1 2 06-data-model.md §6.11, §6.13, 14-share-snapshot-privacy-strategy.md §14.1-14.7
BE-S5-03 Harden production safety and reliability Verify secret-only configuration, server-side validation for snapshot IDs and settings mutations, private data protection, health endpoint behavior, and component fallback contract coverage. AC-19.01, AC-19.02, AC-19.03, AC-19.04, AC-19.05 BE1 3 07-security.md, 08-non-functional-requirements.md, 10-integration-points.md §10.2-10.4, 11-environment-configuration.md

Frontend

Card ID PM Card Title Task Description AC Owner Est Docs
FE-S5-01 Build full share management UI Add owner share controls, delete confirmation, deleted snapshot branded page, safe public rendering, and no-content exposure after deletion. AC-14.01, AC-14.02, AC-14.03, AC-14.04, AC-14.05, AC-14.06, AC-14.07, AC-14.08 FE1 3 14-share-snapshot-privacy-strategy.md §14.1-14.7, 05-module-definitions.md §5.1, §5.11
FE-S5-02 Polish final demo and error states Harden final demo route behavior, branded recoverable errors, privacy-safe empty states, share preview polish, and documented fallback copy. AC-14.07, AC-15.01, AC-18.04, AC-19.05 FE1 2 05-module-definitions.md §5.1, 10-integration-points.md §10.1-10.4, 14-share-snapshot-privacy-strategy.md §14.6
FE-S5-03 Wire full share lifecycle end-to-end Depends on BE-S5-01, BE-S5-02, FE-S5-01, and FE-S5-02; FE-S5-02 lands last, so FE owns the wiring. Verify create, view public URL unauthenticated, static content, safe fields, owner delete, non-owner denial, deleted 410 page, and retention-unavailable public behavior. AC-14.01, AC-14.02, AC-14.03, AC-14.04, AC-14.05, AC-14.06, AC-14.07, AC-14.08, AC-14.09 FE1 3 02-system-architecture.md §2.4, 14-share-snapshot-privacy-strategy.md §14.1-14.7

Technical Lead Scaffold and Verification

Card ID PM Card Title Task Description AC Owner Est Docs
TL-S1-01 Establish app scaffold and quality gates Confirm Next.js app structure, module boundaries, Drizzle scripts, test commands, environment examples, and coding guardrails before Sprint 1 feature cards begin. AC-19.01, AC-19.02 TL 2 02-system-architecture.md §2.1-2.7, 03-repository-structure.md, 04-tech-stack.md, 11-environment-configuration.md
TL-S2-01 Validate judge demo readiness Verify prepared judge account seed, reset procedure, 60-second demo path, minimal share path, and demo completion analytics before Sprint 2 closes. AC-18.01, AC-18.02, AC-18.03, AC-18.04, AC-18.05, AC-18.06, AC-18.07, AC-20.01, AC-20.02 TL 2 05-module-definitions.md §5.9, §5.12, 13-scoring-game-loop-strategy.md §13.8
TL-S4-01 Validate daily.dev contract assumptions Confirm actual daily.dev endpoint behavior, pagination, rate-limit headers, unavailable activity signals, and documented fallback copy before Sprint 4 closes. AC-15.03, AC-15.04, AC-15.05, AC-15.06, AC-17.01, AC-17.02, AC-17.03, AC-17.04, AC-17.05, AC-17.06, AC-17.07, AC-17.08, AC-17.09 TL 2 12-dailydev-integration-strategy.md §12.8, 10-integration-points.md §10.1
TL-S5-01 Run final acceptance and privacy audit Validate full AC coverage, public snapshot privacy boundaries, retention expectations, component fallbacks, production env readiness, and optional US-21 follow-up decision. AC-14.01, AC-14.02, AC-14.03, AC-14.04, AC-14.05, AC-14.06, AC-14.07, AC-14.08, AC-14.09, AC-19.01, AC-19.02, AC-19.03, AC-19.04, AC-19.05, AC-19.08 TL 2 07-security.md, 08-non-functional-requirements.md, 14-share-snapshot-privacy-strategy.md §14.1-14.7

Definition of Done (per card)

  • All cited AC IDs are implemented or explicitly verified by the card.
  • Server-side mutations validate user-controlled input at the boundary.
  • User-owned data is scoped to the authenticated owner.
  • Public routes expose only documented public projections.
  • Tests cover core success, authorization, idempotency, and relevant error paths.
  • UI cards are manually verified in the running app for golden path, loading, empty, and error states.
  • Wiring cards prove the acceptance criteria end-to-end against real frontend and backend code.
  • Documentation references remain valid after implementation.

Summary

Sprint Focus BE cards FE cards BE Est FE Est
Sprint 1 Production foundation, auth, persistence, scoring 6 3 16 8
Sprint 2 Landing, dashboard, demo mode, judge accounts, minimal share 5 6 13 16
Sprint 3 Quests, power-ups, next best action, nudges 3 4 8 11
Sprint 4 daily.dev token, API integration, fallbacks 4 3 11 9
Sprint 5 Full share lifecycle, retention, polish 3 3 8 8