planlisted

# PRD to Plan Break a PRD into phased vertical slices (tracer bullets). **Interactive prompts**: present options as a numbered list and wait for the user's choice. Output: `.tracerkit/plans/<slug>.md`. ## Input The argument (if provided) is: $ARGUMENTS Use argument as `<slug>`. If empty, list PRDs as numbered options and wait for the user's choice. ## Workflow ### 1. Read the PRD Read `.tracerkit/prds/<slug>.md`. If missing, list PRDs as numbered options and wait for the user's choice. If `.tracerkit/plans/<slug>.md` exists, present options and wait: 1. Overwrite existing (Recommended) 2. Pick a 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 PRD:** | PRD Section | Becomes | | ----------------- | ------------------------------------------------ | | New Modules | Implement module with interface