# Planning

<!-- This is a structural guide. Add, remove, or modify sections as needed for this generation. -->

## Goal
<!-- Core section. State this generation's goal clearly and concisely. What will be different when this generation is complete? -->

## Completion Criteria
<!-- Core section. List verifiable completion criteria. Each criterion should be testable — how will you know it's done? -->

## Background
<!-- Optional — include if relevant. Why is this work needed? What problem does it solve or what opportunity does it address? -->

## Brainstorming
<!-- Optional — include for complex goals. Explore the problem space: What are the key questions? What approaches are possible? Use a comparison table if evaluating multiple options. -->

## Approach
<!-- Optional — include if relevant. Describe the chosen approach, architecture decisions, and technology choices. Why this approach over alternatives? -->

## Risk Assessment
<!-- Optional — include if relevant. What could go wrong? What are the unknowns? Are there dependencies on external factors? -->

## Scope
<!-- Optional — include if relevant. List target files/modules to be changed. What is explicitly out of scope? -->

## Tasks
<!-- Core section. Use checklist format: - [ ] T001 `src/path/file.ts` — description. Keep tasks atomic and ordered. Max 20. -->

## Dependencies
<!-- Optional — include if relevant. Specify task dependencies or ordering constraints. -->