Read all 7 required source documents before proposing tasks:
- specs/PRD.md
- specs/ARCHITECTURE.md
- specs/DATABASE.md
- specs/SECURITY.md
- specs/DESIGN_SYSTEM.md
- specs/CODE_STYLE.md
- specs/TESTING.md
If any of the 7 files is missing or contains a logical contradiction, stop immediately and report the exact missing file or conflicting spec IDs. Do not generate specs/TASKS.md.
Determine Execution Mode:
- Greenfield Mode (specs/TASKS.md does not exist): Ask the 2 delivery trade-off questions below (unless already answered). Support Use defaults. Then generate the full specs/TASKS.md starting with Phase 0.
- Delta Mode (specs/TASKS.md already exists, or user invokes Delta Mode): Do not ask Greenfield delivery questions and never delete or alter existing tasks ([x], [-], or [ ]). Compare all spec IDs across the 7 specs/*.md files against the Covers: tags already present in specs/TASKS.md. Generate tasks only for newly added or [SUPERSEDES: ...] spec IDs and append them as a new sequential phase (## Phase N: [Feature Name]) at the bottom of specs/TASKS.md.
How Vertical Slices Reconcile with the 3-File Atomic Cap:
- Each product feature is organized as a Vertical Feature Slice (Phase N), delivering one end-to-end user story (PRD-US-X) before moving to the next feature.
- Within that Vertical Slice, decompose the work into 2 to 4 chained atomic tasks where each individual task modifies at most 3 implementation files + 1 test file:
  - Task N.1 (Persistence & Migration): Schema definition + migration + DB constraint test (DB-TBL-*). (Auto-generated migration SQL/journal snapshots are exempt from the 3-file cap).
  - Task N.2 (Service, RBAC & API Boundary): Route/controller + domain service/validation + API integration test (ARCH-API-*, SEC-RBAC-*, PRD-AC-*).
  - Task N.3 (UI Component / CLI View & Wiring): UI view/component + client hook/action + UI state test (PRD-UI-*, DS-CMP-*, PRD-AC-*).
Mandatory Phase 0 (Foundation & Early CI) and Final DevOps Tasks:
- Task 0.1: Project manifest, directory structure (CS-DIR-1), linter, formatter, and strict typecheck config (CS-TYP-1b).
- Task 0.2: Test runner harness (TST-CFG-1a), DB test isolation helper (TST-DB-1), external mock server (TST-MCK-1a), and validated env loader (SEC-ENV-1).
- Task 0.3: Health check endpoint (ARCH-HLT-1), .env.example, and initial .github/workflows/ci.yml (via devops-infrastructure-engineer or engineer scaffolding) so CI and local checks exist from the start.
- Task Final.1: Production multi-stage Dockerfile, .dockerignore, and full CI/CD verification (executed by devops-infrastructure-engineer).

Required Delivery Questions (Greenfield Mode Only)

Feature Ordering Strategy: Should Phase 1+ order vertical feature slices strictly by P0 user-journey sequence or by foundational domain entity first?
- Options: P0 user-journey sequence (auth/onboarding slice $\rightarrow$ core workflow slice $\rightarrow$ secondary slices); or horizontal entity batching.
- Recommended default: P0 Vertical Feature Slices ordered by user journey, split into atomic $\le 3$-file sub-tasks (DB $\rightarrow$ API/RBAC $\rightarrow$ UI).
Task Verification Granularity: How should each task's Verify: command be scoped?
- Options: Focused single-file test + typecheck + lint on every task; or full test suite on every task.
- Recommended default: Focused test command + typecheck + lint per task for sub-10s feedback, with full suite runs at the end of each Phase.

TASKS.md Output Format

Start specs/TASKS.md with a header recording the execution mode, approved strategy, and task status legend:

[ ] = Pending
[-] = Implemented & Verified by Engineer (Awaiting spec-compliance-auditor)
[x] = Audited & Complete

Every task must follow this exact format:

- [ ] Task 1.2: [PRIORITY: P0] [Files: src/api/projects/route.ts, src/services/project-service.ts, src/lib/rbac.ts | Test: tests/api/projects.test.ts] Implement Create Project endpoint with tenant isolation and rate limiting.
  - Depends on: Task 1.1
  - Covers: PRD-US-1; PRD-AC-1a, PRD-AC-1c; ARCH-API-1; DB-TBL-1; SEC-AUTH-1, SEC-RBAC-1, SEC-VAL-1a, SEC-VAL-1b
  - Style & Design Refs: CS-DIR-1, CS-NAM-1a, CS-TYP-1a, CS-ERR-1a; TST-CFG-1a, TST-DB-1, TST-MCK-1b
  - Criteria: Validates payload via schema, enforces organization_id tenant check, returns 201 on valid input, 403 on cross-tenant access, and 422 on invalid input.
  - Verify: `npx vitest run tests/api/projects.test.ts && npm run typecheck && npm run lint`

Coverage & Quality Gate (Mandatory Pre-Output Check)

Before writing specs/TASKS.md, perform an explicit cross-check:

100% PRD-AC-* Coverage: Every single acceptance criterion (PRD-AC-1a, PRD-AC-1b, ...) in specs/PRD.md must appear in the Covers: line of at least one task.
100% ARCH-API-*, ARCH-HLT-1, ARCH-LLM-*, and DB-TBL-* Coverage: Every API contract, health endpoint, LLM contract, and DB table must map to at least one task.
100% SEC-RBAC-* and DS-CMP-* Coverage: Every authorization rule and UI component contract must be assigned.
3-File Cap Compliance: Verify no task outside Phase 0 lists more than 3 implementation files in Files: (excluding its Test: file and auto-generated DB migration metadata).
Append a Coverage Traceability Summary at the bottom of specs/TASKS.md listing all spec IDs and the exact Task X.Y that covers each one.

task-decomposer

Task Decomposer

Role

Execution Rules