---
description:
globs:
alwaysApply: false
---
# "Task File" Management Guide
<!-- https://github.com/elie222/inbox-zero/blob/main/.cursor/rules/subtask-list.mdc -->
Guidelines for creating and managing subtask lists in markdown files to track project progress

## Task File Creation

1. Create markdown task files under the `.filebundler/tasks` folder:
   - Use a descriptive name relevant to the feature (e.g., `ASSISTANT_CHAT.md`)
   - Include a clear title and description of the feature being implemented

2. Structure the file with these sections:
   ```markdown
   # Feature Name Implementation

   Brief description of the feature and its purpose.

   ## Completed Subtasks

   - [x] Subtask 1 that has been completed
   - [x] Subtask 2 that has been completed

   ## In Progress Subtasks

   - [ ] Subtask 3 currently being worked on
   - [ ] Subtask 4 to be completed soon

   ## Future Subtasks

   - [ ] Subtask 5 planned for future implementation
   - [ ] Subtask 6 planned for future implementation

   ## Implementation Plan

   Detailed description of how the feature will be implemented.

   ### Relevant Files

   - path/to/file1.ts - Description of purpose
   - path/to/file2.ts - Description of purpose
   ```

## Subtask List Maintenance

1. Update the subtask list as you progress:
   - Mark subtasks as completed by changing `[ ]` to `[x]`
   - Add new subtasks as they are identified
   - Move subtasks between sections as appropriate

2. Keep "Relevant Files" section updated with:
   - File paths that have been created or modified
   - Brief descriptions of each file's purpose
   - Status indicators (e.g., ✅) for completed components

3. Add implementation details:
   - Architecture decisions
   - Data flow descriptions
   - Technical components needed
   - Environment configuration

## AI Instructions

When working with task files, the AI should:

1. Regularly update the task file after implementing significant components
2. Mark completed subtasks with [x] when finished
3. Add new subtasks discovered during implementation
4. Maintain the "Relevant Files" section with accurate file paths and descriptions
5. Document implementation details, especially for complex features
6. When implementing subtasks one by one, first check which subtask to implement next
7. After implementing a subtask, update the task file to reflect progress

## Example subtask Update

When updating a subtask from "In Progress" to "Completed":

```markdown
## In Progress Subtasks

- [ ] Implement database schema
- [ ] Create API endpoints for data access

## Completed Subtasks

- [x] Set up project structure
- [x] Configure environment variables
```

Should become:

```markdown
## In Progress Subtasks

- [ ] Create API endpoints for data access

## Completed Subtasks

- [x] Set up project structure
- [x] Configure environment variables
- [x] Implement database schema
```