to-planlisted

# To Plan Turn the source into self-contained local task files and register them in the project's single master plan. Each task is the smallest complete behavior that can be implemented, verified, and merged independently on its own branch. ## Process ### 1. Confirm the source Use a PRD, decision document, or the current conversation. If the source is unclear, ask the user to identify it. The source type never determines the number of tasks. ### 2. Locate or bootstrap the master plan Find the master plan through the most specific `AGENTS.md` `Active plan` entry, falling back to `CLAUDE.md`. - If it exists, append tasks to it. Do not create another plan. - Change an architectural-decision bullet only when the source contains a new durable decision. - If no plan exists, explore the codebase first, create the master plan from the template below, and register it in `AGENTS.md` and in `CLAUDE.md` when that file exists. - On an existing codebase, describe the current architecture and begin the task list with work planned now. Do not backfill shipped work. ### 3. Explore the codebase Inspect the current architecture, domain vocabulary, patterns, integration layers, tests, and relevant decision records. ### 4. Draft the smallest vertical tasks Break the source into tracer-bullet tasks. <vertical-slice-rules> - Create one task for each smallest complete, independently verifiable behavior. - Cross every layer relevant to that behavior, including its tests or verificati