planlisted

# Create Implementation Plan Read the requirements at $ARGUMENTS and create a detailed implementation plan. ## Plan Document Header Every plan MUST start with: ```markdown # [Feature Name] Implementation Plan **Goal:** [One sentence] **Architecture:** [2-3 sentences about approach] **Tech Stack:** [Key technologies] ``` ## Context Gathering Before planning, preload domain context. When dispatching the planner agent, prefix its prompt with: ``` @ATLAS.md (navigation index — use its Where to Look and Module Map tables before any codebase search) @CLAUDE.md (conventions, rules, domain vocabulary) ``` If either file does not exist, omit the corresponding `@` reference. `@` references auto-read on dispatch so the subagent receives them in context; subagents do NOT inherit parent conversation history. **Token discipline:** Do NOT paste file contents or summaries into the dispatch prompt — send task description, file paths, and line ranges only. The planner reads actual files in its own context. Duplicating content in the dispatch wastes tokens (same pattern as build skill). ## Task Structure Each task MUST follow this exact format: ```markdown ### Task N: [Component Name] **Files:** - Create: `exact/path/to/file.py` - Modify: `exact/path/to/existing.py` - Test: `tests/exact/path/to/test.py` **Step 1: Write the failing test** [complete test code] **Step 2: Run test to verify it fails** Run: `[exact command]` Expected: FAIL with "[reason]" **Step 3: Write minimal imp