Cursor rule

1---
2description: Task Workflow System for project implementation across multiple task files within the tasks/ directory.
3globs: **/*
4alwaysApply: true
5---
6 
7# Task Workflow System (Multi-File in `tasks/` Directory)
8 
9- **Purpose:** Standardize task implementation with proper tracking and status updates across a distributed task list.
10- **Implementation:** Tasks are distributed across `tasks/tasks-N.md` files, indexed by `tasks/tasks-index.md`.
11 
12## Overall Task Management Structure
13 
14- **Index File (`tasks/tasks-index.md`):**
15 
16  - Contains the **Overall Project Task Summary** (Total Tasks, Pending, Complete for the _entire_ project).
17  - Contains the **Task File Index**, mapping Task ID ranges to specific `tasks/tasks-N.md` files.
18 
19```markdown
20    ## Overall Project Task Summary
21 
22    - **Total Tasks**: {Total for project}
23    - **Pending**: {Pending for project}
24    - **Complete**: {Complete for project}
25 
26    ## Task File Index
27 
28    - `tasks/tasks-1.md`: Contains Tasks {start_id_1} - {end_id_1} ({task_count_1} tasks)
29    - `tasks/tasks-2.md`: Contains Tasks {start_id_2} - {end_id_2} ({task_count_2} tasks)
30    - ...
31```
32 
33- **Task Files (`tasks/tasks-N.md`):**
34 
35  - Each file starts with its own local summary:
36 
37```markdown
38    ## Summary (tasks-N.md) // Clarify which task file this summary is for
39 
40    - **Tasks in this file**: {Count for this file}
41    - **Task IDs**: {start_id_N} - {end_id_N} // e.g., 001 - 030
42```
43 
44  - Followed by the `## Tasks` section containing individual tasks.
45 
46- **Task Structure (within `tasks/tasks-N.md`)**
47 
48  - Tasks are defined with:
49 
50```markdown
51    ### Task ID: {ID}
52 
53    - **Title**: Example title
54    - **File**: example/file/path (relative to project root, excluding project root dir)
55    - **Complete**: [ ]
56 
57    #### Prompt:
58 
59    ```markdown
60    DETAILED PROMPT INCLUDING TARGET FILE PATH AND CONTEXT
61```
62```
63 
64```
65 
66```
67 
68## Task Management Workflow
69 
70### 1. Locating a Task
71 
72- **When user requests "next task":**
73  1. Open and consult `tasks/tasks-index.md` to understand the overall project status and identify the sequence of task files.
74  2. Iterate through `tasks/tasks-1.md`, `tasks/tasks-2.md`, etc., in numerical order as listed in the index.
75  3. Within each `tasks/tasks-N.md` file, find the first task where `Complete: [ ]`. This is the next task.
76  4. Note the `tasks/tasks-N.md` file this task resides in.
77- **When user specifies a Task ID (e.g., "Task 042"):**
78  1. Open and consult `tasks/tasks-index.md`.
79  2. Read the "Task File Index" to determine which `tasks/tasks-N.md` file contains that Task ID.
80  3. Open the identified `tasks/tasks-N.md` file (e.g., if Task 042 is in `tasks-2.md`, open `tasks/tasks-2.md`).
81  4. Locate the task with the specified `### Task ID: {ID}`.
82 
83### 2. Task Implementation
84 
85- **Always review overall project context as needed:**
86  ```javascript
87  // ✅ DO: If architectural context is needed, refer to `docs/architecture.md` and other relevant architecture documents located in the `docs/` directory.
88  // The task prompt itself should be the primary guide for implementation details.
89```
90- **Implement each task according to its prompt and specified `File` path.**
91```javascript
92  // ✅ DO: Focus implementation *only* on the file specified in the task's "File:" field.
93  // ✅ DO: Follow the detailed instructions, context, and references within the task's "Prompt:" section.
94```
95 
96### 3. Updating Task Status (Critical)
97 
98- After successfully implementing a task:
99  1. **Locate the task** within its specific `tasks/tasks-N.md` file (as identified in Step 1).
100  2. **Change its status:** Modify `Complete: [ ]` to `Complete: [x]` in that specific `tasks/tasks-N.md` file.
101  3. **Update the local summary within that `tasks/tasks-N.md` file (Optional but Recommended):**
102     - If feasible, decrement "Pending" and increment "Complete" counts for _that file's specific summary_. This is secondary to updating the main index.
103  4. **Update the Overall Project Task Summary in `tasks/tasks-index.md`:**
104     - Decrement "Pending" by 1.
105     - Increment "Complete" by 1.
106  5. **Save changes** to both the modified `tasks/tasks-N.md` file and `tasks/tasks-index.md`.
107```javascript
108  // ✅ DO: Update "Complete: [ ]" to "Complete: [x]" in the correct `tasks/tasks-N.md` file.
109  // ✅ DO: Update "Pending" and "Complete" counts in `tasks/tasks-index.md`.
110  // ❌ DON'T: Modify task IDs, titles, or prompts unless explicitly instructed for a correction.
111```
112 
113### 4. Notification
114 
115- Inform the user of successful task completion.
116- Provide a summary of changes made (files modified).
117- State the Task ID and Title of the completed task and which `tasks/tasks-N.md` file it was in.
118 
119## Task Creation Guidelines (If AI needs to add/modify tasks)
120 
121- **Adding New Tasks Based on User Requests:**
122 
123  1. **Determine Target Task File:** The user or AI must decide which `tasks/tasks-N.md` file the new task belongs to.
124     - If inserting into an existing sequence, identify the `tasks/tasks-N.md` file.
125     - If adding to the very end of the project and the last `tasks-N.md` is full (e.g., based on line count or task count), a new `tasks/tasks-N+1.md` file might need to be conceptually created (the Task Master agent would typically handle new file creation).
126  2. **ID Assignment:**
127     - **End of a `tasks/tasks-N.md` file:** Use the next sequential number based on the highest ID _globally_ (from `tasks/tasks-index.md` "Total Tasks").
128     - **Between Existing Tasks (within a `tasks/tasks-N.md` file):** Use decimal extension format (e.g., 002-1, 002-2).
129```javascript
130     // ✅ DO: Ensure Task ID reflects implementation order.
131     // ✅ DO: Use decimal extension for insertions.
132```
133  3. **Structure:** Add the task to the chosen `tasks/tasks-N.md` file using the standard Task Structure.
134  4. **Update Summaries:**
135     - Update the local summary in the modified `tasks/tasks-N.md` file (increment "Tasks in this file", adjust ID range if necessary).
136     - Update the "Total Tasks" and "Pending" counts in `tasks/tasks-index.md`.
137     - If a new `tasks/tasks-N+1.md` file was notionally created, update the Task File Index in `tasks/tasks-index.md`.
138 
139- **Task Template (for reference when creating new tasks):**
140 
141```markdown
142  ### Task ID: [ID]
143 
144  - **Title**: [Concise description]
145  - **File**: [Target file path, no project root, e.g., src/components/MyComponent.js]
146  - **Complete**: [ ]
147 
148  #### Prompt:
149 
150  ```markdown
151  **Objective:** ...
152  **File to Create/Modify:** {e.g., src/components/MyComponent.js}
153  **User Story Context:** ...
154  **Detailed Instructions:**
155  ...
156  **Acceptance Criteria (for this task):**
157  ...
158```
159```
160 
161## Navigation and File Management within `tasks/` Directory
162 
163- **To find the "next pending task":**
164  1. Open `tasks/tasks-index.md`. Review the "Task File Index".
165  2. Starting with `tasks/tasks-1.md` (or the first file listed in the index), open it.
166  3. Scan for the first task with `Complete: [ ]`. If found, this is the target task and its file.
167  4. If not found in the current file, proceed to the next `tasks/tasks-N.md` file listed in the index and repeat step 3.
168- **To find a specific Task ID `{ID}`:**
169  1. Open `tasks/tasks-index.md`.
170  2. Read the "Task File Index" to identify which `tasks/tasks-N.md` file contains Task ID `{ID}`.
171  3. Open that specific `tasks/tasks-N.md` file (e.g., if `tasks-index.md` indicates Task 042 is in `tasks/tasks-2.md`, then open `tasks/tasks-2.md`).
172  4. Search within that file for `### Task ID: {ID}`.
173- **When updating task status:**
174  1. Identify the correct `tasks/tasks-N.md` file for the task being updated.
175  2. In that specific file, modify `Complete: [ ]` to `Complete: [x]`.
176  3. **Critically, open `tasks/tasks-index.md` and update the "Overall Project Task Summary" (Pending and Complete counts).**
177  4. Ensure both modified files (the `tasks/tasks-N.md` and `tasks/tasks-index.md`) are saved.
178 
179## Important Considerations for the AI IDE Agent
180 
181- All task-related files (`tasks-index.md` and `tasks-*.md`) are located within the `tasks/` directory at the root of the project.
182- The `tasks/tasks-index.md` file is the **primary source of truth for overall project progress and for locating tasks within the specific `tasks/tasks-N.md` files.**
183- Always update `tasks/tasks-index.md`'s summary when a task in any `tasks/tasks-N.md` file is marked complete.
184- When asked for the "next task," ensure you are checking files in the correct numerical order as indicated by the `tasks/tasks-index.md`.
185- All other project documentation (PRD, Architecture, Stories, etc.) is expected to be in a `docs/` directory at the root of the project.
186 
187```