Implementation Plan: [FEATURE]

Branch: [###-feature-name] | Date: [DATE] | Spec: [link] Input: Feature specification from /specs/[###-feature-name]/spec.md

Note: This template is filled in by the /speckit.plan command. See .specify/templates/commands/plan.md for the execution workflow.

Summary

[Extract from feature spec: primary requirement + technical approach from research]

Technical Context

Language/Version: TypeScript 5.x strict mode
Primary Dependencies: Next.js 16+, Drizzle ORM, Shadcn UI, NextAuth.js
Storage: PostgreSQL
Testing: Jest/Vitest for unit tests, Playwright for E2E
Target Platform: Docker containers, web browsers
Project Type: Web application (Next.js)
Performance Goals: <2s page load, <500ms API responses
Constraints: Server-first architecture, no client fetches, Azure AD only
Scale/Scope: Multi-tenant SaaS, 1000+ concurrent users

Constitution Check

GATE: Must pass before Phase 0 research. Re-check after Phase 1 design.

Uses Next.js App Router with Server Actions (no client-side fetches)
TypeScript strict mode enabled
Drizzle ORM for all database operations
Shadcn UI for all new components
Azure AD multi-tenant authentication
Docker deployment with standalone build

Project Structure

Documentation (this feature)

specs/[###-feature]/
├── plan.md              # This file (/speckit.plan command output)
├── research.md          # Phase 0 output (/speckit.plan command)
├── data-model.md        # Phase 1 output (/speckit.plan command)
├── quickstart.md        # Phase 1 output (/speckit.plan command)
├── contracts/           # Phase 1 output (/speckit.plan command)
└── tasks.md             # Phase 2 output (/speckit.tasks command - NOT created by /speckit.plan)

Source Code (repository root)

# [REMOVE IF UNUSED] Option 1: Single project (DEFAULT)
src/
├── models/
├── services/
├── cli/
└── lib/

tests/
├── contract/
├── integration/
└── unit/

# [REMOVE IF UNUSED] Option 2: Web application (when "frontend" + "backend" detected)
backend/
├── src/
│   ├── models/
│   ├── services/
│   └── api/
└── tests/

frontend/
├── src/
│   ├── components/
│   ├── pages/
│   └── services/
└── tests/

# [REMOVE IF UNUSED] Option 3: Mobile + API (when "iOS/Android" detected)
api/
└── [same as backend above]

ios/ or android/
└── [platform-specific structure: feature modules, UI flows, platform tests]

Structure Decision: [Document the selected structure and reference the real directories captured above]

Complexity Tracking

Fill ONLY if Constitution Check has violations that must be justified

Violation	Why Needed	Simpler Alternative Rejected Because
[e.g., 4th project]	[current need]	[why 3 projects insufficient]
[e.g., Repository pattern]	[specific problem]	[why direct DB access insufficient]

3.6 KiB Raw Blame History