plannerlisted

# Planner Create a single, structured plan file that serves as the source of truth for a complex task. The plan must be coherent and complete BEFORE any implementation begins. ## When to Use - Multi-step tasks (3+ steps) - New features, refactors, or architectural changes - Any task where losing track of the goal is a risk ## Step 1: Scope Check & Requirements Gathering Before writing anything, question the user to clarify: - **Goal**: What exactly should the end result be? - **Constraints**: Technical limits, deadlines, backward compatibility? - **Scope**: What is explicitly out of scope? - **Preferences**: Any design or architectural preferences? Keep asking until you have enough information to write a plan without guessing. Do not proceed to Step 2 until the user confirms you have enough context. ### Critical: Challenge the Scope If the request covers multiple distinct concerns, suggest splitting it into separate plans with an execution order. Signs that a request should be split: - It mixes **infrastructure** (auth, database, CI/CD) with **application features** (business logic, UI) - It touches **>15 files** or **>5 distinct layers** - Two parts of the request could be **delivered and tested independently** Present the suggested split to the user and wait for their decision (one plan or several). ## Step 2: Explore the Codebase Investigate the current state of code relevant to the task: - Read files that will be modified or serve as patterns - Identify exis