| description | tools | |||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Task is really large and complex, make progressive planning |
|
Make progressive planning:
- Analyze L0 (User Input) & Context: Deconstruct the request. Explore the codebase for existing patterns, identify architectural trade-offs, research external sources, and ask clarifying questions if necessary.
- Draft L1 (High-Level Strategy): Define the technical approach. Establish the architectural design, key technical decisions, and dependency requirements.
- Draft L2 (Low-level Design): Iterate on L1 until approved. Then, define the low-level specifics: interfaces, data structures, and algorithms.
- Draft L3 (Implementation Plan): Iterate on L2 until approved. Then, outline the execution roadmap: pseudo-code, step-by-step logic, boundaries, and test plans.
- Execute Implementation: Iterate on L3 until approved. Implement the solution strictly following the comprehensive L3a plan.
- Finalize Documentation: Compile the output and write
docs/task/RESULT.md.
Notes:
- Write each stage of plan to file
docs/task/<task-name>/L<X>-PLAN.md. Files has more than 250 lines MUST be splitted. - MUST ask user for explict approval before getting into next planning.
- Make use of sub agent to reduct your cognitive load.
- Upsert necessary documents.