TODO-tracking

---

description: TODO Tracking System - Automatically create and maintain TODO files for features and tasks globs:

• "**/*.{js,jsx,ts,tsx,py,go,rs,java,c,cpp,cs,rb,php,swift,kt,scala,r,m,dart,lua,jl,ex,clj,hs,ml,fs,v,vb,sql,sh,ps1,yaml,yml,json,xml,html,css,scss,sass,less,md,mdx,vue,svelte}"
• "**/TODO/*.md"

---

TODO Tracking System

A system for creating and maintaining TODO files that document the step-by-step process of implementing features, similar to Claude Code's checkpoint system.

content: |

TODO Tracking System Instructions

When /TODO is detected or this rule is relevant, follow these guidelines:

1. TODO File Creation

When starting a new feature or task:

• Create a file in ./TODO/ directory named: YYYY-MM-DD_<task-name>.md
• Use kebab-case for task names (e.g., 2024-01-15_user-authentication-system.md)
• If TODO directory doesn't exist, create it first

2. TODO File Structure

Each TODO file should follow this template:

# TODO: [Task Name]

**Created:** [Date]
**Status:** 🔄 In Progress | ✅ Complete | ⏸️ Paused | ❌ Blocked
**Priority:** 🔴 High | 🟡 Medium | 🟢 Low
**Related Files:** [List key files that will be modified]
**Issue/Ticket:** #[number] (if applicable)

## Overview
[Brief description of what we're implementing]

## Success Criteria
- [ ] [Specific measurable outcome 1]
- [ ] [Specific measurable outcome 2]
- [ ] [Specific measurable outcome 3]

## Dependencies

[Feature Name] ├── [Component 1] ✅ ├── [Component 2] 🔄 │ ├── [Subcomponent 2.1] ✅ │ └── [Subcomponent 2.2] ⏳ └── [Component 3] ⏳

## Implementation Steps

### Step 1: [Step Name] ✅
**Status:** Complete
What we did:
- [Action taken]
- [Files modified]
- [Key decisions made]

```[language]
// Code snippet showing the implementation

✓ Checkpoint: [What works at this point] Commit: [hash] - "[commit message]"

Step 2: [Step Name] 🔄

Status: In Progress

What we're doing:

• [Current action]
• [Expected outcome]

Blockers: [Any issues encountered]

Step 3: [Step Name] ⏳

Status: Pending

What we need to do:

• [Planned action]
• [Dependencies]

Error Log

Error 1: [Date]

Error: [Error message] Context: [Where it occurred] Solution: [How it was fixed] Prevention: [How to avoid in future]

Notes & Decisions

• [Date]: [Important decision or note]
• [Date]: [Why we chose approach A over B]
• [Date]: [Architectural decision]

Code Snippets & Solutions

[Problem/Feature Name]

// Reusable code solution

Why this works: [Explanation]

Next Session

When returning to this task:

1. [First thing to check/do]
2. [Second thing to check/do]
3. [Continue from: specific file and line]

Pre-Completion Checklist

• All tests passing
• Code reviewed / AI-reviewed
• Documentation updated
• Edge cases handled
• Error handling implemented
• Security considerations addressed

Resources

• [Relevant documentation links]
• [Reference implementations]
• [Stack Overflow solutions that helped]

### 3. During Implementation
As you work through the task:

1. **Update status in real-time**:
   - Mark steps as ✅ Complete, 🔄 In Progress, ❌ Blocked, or ⏳ Pending
   - Remove time tracking - we work at AI speed!

2. **Document decisions**:
   - Why did we choose approach A over B?
   - What trade-offs did we make?
   - What assumptions are we making?

3. **Create checkpoints**:
   - After each significant step, note what's working
   - Include git commit hashes for major checkpoints
   - This helps with debugging and rolling back if needed