planlisted

# Plan Break a spec into phased vertical slices (tracer bullets). Output: `.specs/plans/<slug>.md`. ## Input The argument (if provided) is: $ARGUMENTS Use argument as `<slug>`. If empty, list specs as numbered options and wait for the user's choice. ## Workflow ### 1. Read the spec Read `.specs/specs/<slug>.md`. If missing, list specs as numbered options and wait for the user's choice. If `.specs/plans/<slug>.md` exists, ask: overwrite (Recommended) or new name. ### 2. Explore the codebase Map architecture, patterns, integration points. Skip if codebase context exists from prior step. **Research protocol**: codebase first, then docs. Unverifiable claims → flag as uncertain, never fabricate. ### 3. Identify durable architectural decisions Before slicing, extract decisions that hold across all phases: - Route structures / URL patterns - Database schema shape - Key data models and definitions - Auth/authorization approach - Third-party service boundaries ### 4. Draft vertical slices Each phase: thin vertical slice through all layers (schema → service → API → UI �� tests). Demoable alone. **Deriving tasks from the spec:** | Spec Section | Becomes | | ----------------- | ------------------------------------------------ | | New Modules | Implement module with interface | | Schema Changes | Migration + validation | | API Contracts | Route returning shape