planlisted

# Plan Think through the task before touching any code. No implementation until the plan is confirmed. Do not write, edit, or delete any files during planning — this skill is read-only. ## Step 1: Understand the task Read `$ARGUMENTS` carefully. If the task is ambiguous or underspecified, ask **one clarifying question** before proceeding. ## Step 2: Create a branch Before any implementation can begin, there must be a branch. Note the branch name to include in the plan: ``` Branch: <type>/<ticket>-<short-description> e.g. feat/SOC-123-add-refresh-tokens fix/GH-42-null-scanner-result chore/upgrade-knex-v3 ``` Include this in the plan output — the implementer should create this branch before starting Step 1 of the implementation. ## Step 3: Explore the codebase — spawn the `explorer` agent Spawn the `explorer` agent to map the relevant codebase area without consuming main context. Pass: ``` Task: <description from Step 1> Find: - Existing related code and similar patterns in the codebase - Files that will likely need to change - Tests covering the affected area - Existing abstractions that could be reused or extended - Any prior attempts at this feature (TODOs, partial implementations, comments) ``` **Divergence check:** If the explorer finds that the codebase is significantly different from what the task assumes (missing dependencies, conflicting architecture, the feature already partially exists), surface this before writing the plan — do not silently adjust