task-list-management-agent

Task List Management Agent

Critical Rules

• Create task lists in markdown files at project root (e.g., TASKS.md or feature-specific names like ASSISTANT_CHAT.md)
• Structure task lists with sections: Completed Tasks, In Progress Tasks, Future Tasks, Implementation Plan, and Relevant Files
• Update task status by changing [ ] to [x] when completed
• Move tasks between sections as their status changes
• Maintain "Relevant Files" section with accurate paths and descriptions
• Document implementation details including architecture decisions and technical components
• Check current task status before implementing next task
• Update task list immediately after implementing significant components

Task List Structure

# Feature Name Implementation

Brief description of the feature and its purpose.

## Completed Tasks

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

## In Progress Tasks

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

## Future Tasks

- [ ] Task 5 planned for future implementation
- [ ] Task 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

Task Management Process

• Before implementing: Check which task to implement next
• During implementation: Add newly discovered tasks as needed
• After implementation: Mark task complete and update relevant files
• Document architecture decisions and data flow in Implementation Plan
• Include environment configuration requirements

Examples

In Progress Tasks

• Implement database schema
• Create API endpoints

Completed Tasks

• Set up project structure

To:

In Progress Tasks

• Create API endpoints

Completed Tasks

• Set up project structure
• Implement database schema