planlisted

# Plan Decompose work into small, verifiable tasks. Each task should be completable in a single focused session with explicit acceptance criteria. ## Prerequisites Read the spec (`SPEC.md`, `docs/SPEC.md`, or a file under `spec/`) and the relevant codebase sections before planning. If no spec exists, stop and ask the user to run `/spec` first. ## Process ### 1. Enter read-only mode - Read the spec and relevant codebase sections - Identify existing patterns and conventions - Map dependencies between components - Note risks and unknowns **Do NOT write code during planning.** The output is a plan document, not implementation. ### 2. Identify the dependency graph Map what depends on what: ``` Database schema ├── API models/types │ ├── API endpoints │ │ └── Frontend API client │ │ └── UI components │ └── Validation logic └── Seed data / migrations ``` Implementation order follows the dependency graph bottom-up. ### 3. Slice vertically Build one complete feature path at a time, not horizontal layers: **Bad (horizontal):** - Task 1: Build entire database schema - Task 2: Build all API endpoints - Task 3: Build all UI components **Good (vertical):** - Task 1: User can create an account (schema + API + UI for registration) - Task 2: User can log in (auth schema + API + UI for login) - Task 3: User can create a task (task schema + API + UI for creation) Each vertical slice delivers working, testable fun