Cursor rule

1---
2description: 
3globs: 
4alwaysApply: false
5---
6---
7description: 
8globs: 
9alwaysApply: false
10---
11# Task List Management
12 
13Guidelines for managing task lists in markdown files to track progress on completing a PRD
14 
15## Task Implementation
16- **One sub-task at a time:** Do **NOT** start the next sub‑task until you ask the user for permission and they say "yes" or "y"
17- **Completion protocol:**  
18  1. When you finish a **sub‑task**, immediately mark it as completed by changing `[ ]` to `[x]`.
19  2. If **all** subtasks underneath a parent task are now `[x]`, follow this sequence:
20    - **First**: Run the full test suite (`pytest`, `npm test`, `bin/rails test`, etc.)
21    - **Only if all tests pass**: Stage changes (`git add .`)
22    - **Clean up**: Remove any temporary files and temporary code before committing
23    - **Commit**: Use a descriptive commit message that:
24      - Uses conventional commit format (`feat:`, `fix:`, `refactor:`, etc.)
25      - Summarizes what was accomplished in the parent task
26      - Lists key changes and additions
27      - References the task number and PRD context
28      - **Formats the message as a single-line command using `-m` flags**, e.g.:
29 
30```
31        git commit -m "feat: add payment validation logic" -m "- Validates card type and expiry" -m "- Adds unit tests for edge cases" -m "Related to T123 in PRD"
32```
33  3. Once all the subtasks are marked completed and changes have been committed, mark the **parent task** as completed.
34- Stop after each sub‑task and wait for the user's go‑ahead.
35 
36## Task List Maintenance
37 
381. **Update the task list as you work:**
39   - Mark tasks and subtasks as completed (`[x]`) per the protocol above.
40   - Add new tasks as they emerge.
41 
422. **Maintain the "Relevant Files" section:**
43   - List every file created or modified.
44   - Give each file a one‑line description of its purpose.
45 
46## AI Instructions
47 
48When working with task lists, the AI must:
49 
501. Regularly update the task list file after finishing any significant work.
512. Follow the completion protocol:
52   - Mark each finished **sub‑task** `[x]`.
53   - Mark the **parent task** `[x]` once **all** its subtasks are `[x]`.
543. Add newly discovered tasks.
554. Keep "Relevant Files" accurate and up to date.
565. Before starting work, check which sub‑task is next.
576. After implementing a sub‑task, update the file and then pause for user approval.