Overview

Weekly development cadence for Phase 2 builds using Elevaite's default tech stack and Cloud Code workflow. This process covers the prep-build-demo-retro cycle with commit-per-step discipline and QA loops to ship narrow vertical slices in client-owned repos.

Before You Start

PRD is locked and approved (per 01-DISCOVERY-TO-PRD.md)
Cloud Code installed with --bypass-permissions enabled
Client repo set up under GitHub thaddeuselevaite/<project-slug>
Vercel deployment configured under ElevaiteWorks team
Default tech stack confirmed: Next.js 16 + React 19 + TypeScript + Tailwind 4, Supabase, Anthropic Claude Sonnet 4.6, Resend
Phase 1/2/3 breakdown documented in PRD

Steps

Review PRD Phase 1 requirements and identify the 3-5 step v1 workflow to build
Set up core data model in Supabase Postgres with seed data
Build feature implementation using Cloud Code with --bypass-permissions
Verify build works: run npx tsc --noEmit && npx next build - both must pass
Perform Playwright spot-check: open new surface in browser, click happy path, take screenshots
Cross-check implementation against PRD requirements
Add changed files with git add <specific-files> (don't use git add .)
Commit with descriptive message: git commit -m "<descriptive message>" with HEREDOC body if meaningful
Push to main: git push origin main
Verify auto-deployment triggers on Vercel
For UI-heavy work: perform multi-pass visual comparison against reference materials
Implement audit log table recording every action for IP defense and compliance
Set up real AI calls for core scoring/parsing/generation using Anthropic Claude Sonnet 4.6
Configure daily/weekly automated email via Resend if applicable
Build Operations/KPIs dashboard for client desk-at-a-glance view
Add auth in some form (even shared password gate to start)
Repeat commit-per-step cycle for each meaningful change throughout build

Quality Check

Git log reads as chronological narrative of what was built and when
Every Phase 1 feature from PRD has working surface
Build + tsc clean passes
Audit log fires on every action
Daily report sends to real inbox (if applicable)
Operations dashboard exists and reads live data
Empty states on every list page
Settings page allows client to tune knobs without code changes
CSV export available from every list page
Walked demo path (3-10 steps) tested end-to-end

Common Issues

Session breaks from misread instruction: Use git revert HEAD to return to known-good state instead of git reset --hard
Deviations from default tech stack: Document written reason in decisions/ folder (e.g. "Client requires Snowflake → Postgres-on-Snowflake compromise")
Phase 2 items blocked: Explicitly list in User testing tab as "Skip — vendor decision pending" so client doesn't test unbuilt features
Visual work differences: Never present without two comparison passes - list every difference and fix all before re-comparing

Phase 2 Weekly Build Cadence