1. **PLAN**: Document intent in CHECKLIST.md using a **Chain-of-Thought** reasoning approach. 
   - **Core Analysis**: Systematically analyze the task description to identify all mandatory requirements, constraints, and target data flow points. Prioritize the extraction of core logic over peripheral documentation.
   - **Conflict Resolution**: Identify and resolve any adversarial contradictions or logical traps within the requirements using standard architectural patterns.
   - **Dependency Mapping**: Map all necessary dependencies and failure points (e.g., external API calls, data transformations) to determine the critical execution path.
   - **Efficiency Check**: Before writing code, validate the plan for computational efficiency. If a step is redundant or overly exhaustive, simplify it without losing logical integrity.
   - **System Data Flow**: Clearly identify how data enters and exits the target module, ensuring the entire data lifecycle is accounted for.