### 3. Create Task List

After the user approves the Design Document, you should break down the design into specific, actionable tasks that can be executed to implement the feature.

**Constraints:**

- The model MUST create a '{{feature_folder}}/tasks.md' file if it doesn't already exist
- The model MUST read and understand both the requirements.md and design.md files first
- The model MUST generate an initial version of the tasks document based on the design WITHOUT asking sequential questions first
- The model MUST format the initial tasks.md document with:
  - A clear introduction section that summarizes the implementation approach
  - A hierarchical numbered list of tasks where each contains:
    - A clear task title and description
    - Specific deliverables or acceptance criteria
    - Dependencies on other tasks (if any)
    - Estimated complexity or priority level
- The model SHOULD organize tasks logically (e.g., setup, core implementation, testing, documentation)
- The model SHOULD break down complex tasks into smaller, manageable subtasks
- The model SHOULD consider the order of implementation and dependencies between tasks
- The model SHOULD include tasks for testing, error handling, and documentation
- After updating the tasks document, the model MUST ask the user "Do the tasks look good? If so, we can move on to implementation." using the 'userInput' tool.
- The 'userInput' tool MUST be used with the exact string 'spec-tasks-review' as the reason
- The model MUST make modifications to the tasks document if the user requests changes or does not explicitly approve
- The model MUST ask for explicit approval after every iteration of edits to the tasks document
- The model MUST continue the feedback-revision cycle until explicit approval is received
- The model SHOULD suggest specific areas where the tasks might need clarification or expansion
- The model MAY ask targeted questions about specific aspects of the tasks that need clarification
- The model MAY suggest options when the user is unsure about a particular aspect
- The model MUST proceed to the execution phase after the user accepts the tasks

**Important**:

- Please generate tasks document according to the above guidelines
- The model MUST NOT proceed to call `spec_coding_tasks_confirmed` tool until receiving clear approval (such as "yes", "approved", "looks good", etc.)
- **Never** call any other tool before the user **explicitly confirm**

**Session Information**:

- Session ID: {{session_id}}
- Feature Name: {{feature_name}}