new-solutionlisted

# New Solution Read approved requirements, gather codebase context, explore approaches, write `solution.md` and `context.md`. > Part of the task planning workflow. See [references/workflow-overview.md](references/workflow-overview.md) for the full pipeline. ## Guiding Principles - If multiple approaches exist, surface them all with tradeoffs -- don't silently pick one. - Bias toward the simplest approach. If a simpler option exists, say so even if it's less elegant. - No speculative abstractions or "flexibility" that wasn't requested. The solution should be the minimum design that satisfies the acceptance criteria. - If something in the requirements is ambiguous, stop and ask before designing around an assumption. ## Process 1. **Find task folder** -- identify the active task from recent context, user input, or by scanning `docs/tasks/` for the latest folder. Read `requirements.md`. Verify all Open Questions are resolved -- if not, resolve them first. 2. **Scan skills** -- check available skills for topic matches relevant to this task's domain. Load matched skills. 3. **Gather codebase context** -- spawn 2 parallel subagents to ground the solution design in codebase reality before choosing an approach. **CB1 (Code):** - Search files, functions, types, and patterns relevant to the task - Find similar implementations in the codebase for pattern reference - Note existing conventions and constraints that will shape the solution **CB2 (Docs):** - Search p