Now I have everything I need. Let me build the plan page with a dark, developer-tool aesthetic with teal as the accent.

Now let me build all the components and the main page:

Here is your complete SaaS MVP Development Plan — a structured, interactive reference document built as a live Next.js app. Here's what's included:

6 interactive sections:

• Sprint Progress — visual per-phase completion bars across the 14-day sprint
• Milestone Timeline — 6 collapsible phases with 24 individual tasks, each tagged with day, status (done / in-progress / planned), and implementation detail
• Feature Matrix — 14 features filterable by MVP In / Post-MVP / Out of Scope, with priority (P0–P2) and effort dots
• Database Schema — full Postgres table designs for users, organizations, sessions, and invitations with PK/FK annotations
• Deployment Pipeline — 4-stage flow (Local → Preview → Staging → Production) with per-stage checklists
• Risk Register — 6 identified risks (3 high, 2 medium, 1 low) each with a concrete mitigation strategy

The key insight for your 1–2 week timeline: lock the schema by end of Day 4, build API routes against stable types, and use Neon's branching or Supabase's preview environments so every PR has its own isolated database — this eliminates the most common cause of late-stage MVP delays.

Let me read the agent examples to understand the proper patterns: