new-planlisted

# New Plan Read requirements + solution, gather codebase context, write `context.md` and `plan.md`. > Part of the task planning workflow. See [references/workflow-overview.md](references/workflow-overview.md) for the full pipeline. ## Process ### Phase 1: Context Gathering Spawn 3 parallel subagents to gather context. Each returns structured findings. **CB1 (Code):** - Search files, functions, types, and patterns relevant to the task - Check file paths mentioned in solution.md -- verify they exist, note current signatures and structure - Find similar implementations in the codebase for pattern reference **CB2 (Docs):** - Search project documentation for relevant how-tos, concept docs, and architecture guides - Check for related rules or conventions that apply - Note any documented constraints or patterns the implementation must follow **CB3 (History):** - Search git commits for related changes - Check `docs/tasks/` for related completed tasks - Note relevant decisions or patterns from past work ### Phase 2: Write context.md Combine findings from all 3 subagents into `context.md` using the template below. Include only verified facts -- paths, snippets, descriptions grounded in actual code. ### Phase 3: Write plan.md Using requirements.md, solution.md, and the freshly written context.md: 1. Break the solution into atomic phases (each phase = one subagent during execution) 2. Define the execution DAG -- which phases depend on which 3. List concrete steps within each