Cursor Task Management System

A systematic approach to managing development tasks using markdown files as scratchpads, with built-in learning mechanisms and progress tracking.

Overview

This skill establishes a structured workflow where each task is documented in a dedicated markdown file with clear requirements, progress tracking, and lessons learned. It emphasizes continuous improvement by recording reusable insights and corrections in the project's `.cursorrules` file.

Instructions

Task File Management

When you receive a new task:

1. **Create a task file** in the `tasks/` folder with format: `{task-order}-{task-brief-description}.md`

- Use clear, descriptive names (e.g., `01-implement-auth-flow.md`)

- Review and clear old different tasks if necessary

2. **Structure each task file with 5 sections:**

**1. Task Overview**

A brief summary of the task's purpose and scope.

**2. Task Status**

One of: `"Planning"`, `"In Progress"`, or `"Done"`

- **Planning**: Clarify requirements and outline approach

- **In Progress**: Actively working on implementation

- **Done**: All subtasks completed, awaiting user review

Update status whenever you receive user feedback or requirements change.

**3. Requirements**

Detailed specifications and expectations from the user.

**4. Scratchpad**

Working area for todos and execution plans. Use task markers:

```

[X] Completed task

[ ] Pending task

```

Update progress as you complete subtasks. Refer to this section when planning next steps.

**5. Task Lessons**

Insights, mistakes, or best practices learned. Summarize key lessons into the `.cursorrules` Lessons section.

3. **Clarify requirements** with the user before starting work to ensure comprehensive planning.

4. **Confirm with user** after creating the task file before proceeding.

Progress Management

- Reflect on progress in the Scratchpad

- Plan next steps

- Request user feedback before continuing

Learning System

**Record lessons in `.cursorrules` file when you discover:**

This prevents repeating the same mistakes and builds project-specific knowledge.

Historical Context

After Task Completion

1. Write lessons learned to `.cursorrules` Lessons section

2. Ensure task status is set to "Done"

3. Keep task file available for future reference

Project-Specific Context

**User Specified Lessons:**

Constraints

Best Practices