# Local Task Tracker

> Work item status management rules and tracker structure for FlowMaster runs

- Skill: `eron1703/local-task-tracker` (Agent Skill)
- Install (CLI): `npx skillmds@latest add eron1703/local-task-tracker`
- Raw SKILL.md: https://api.skillmd.com/api/skills/eron1703/local-task-tracker/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Productivity
- Author: eron1703 (https://skillmd.com/u/eron1703)
- Updated: 2026-09-10
- Page: https://skillmd.com/skills/eron1703/local-task-tracker

---


# Local Task Tracker

## Status System

See core-rules for the 4-status work item system (pending/started/untested/accepted).

## Tracker Structure

The tracker is a single unified list in the run directory:

```
<run-dir>/
├── TRACKER.md     # Index table (one flat list: #, summary, priority, status, assigned)
├── 001.md         # Individual item detail files
├── 002.md
├── ...
└── 025.md
```

### TRACKER.md (Index)
- **One flat list** — no separate sections for fixes vs CRs vs feedback
- Compact table with columns: **#** (linked to .md file), **Summary** (Module + what needs to change), **Priority**, **Status**, **Assigned**
- Each # links to its detail file: `[001](001.md)`
- Items numbered sequentially 001-NNN

### Individual Item Files (NNN.md)
Each file contains:
- **Status** and metadata (reported date, component, services, previously known as)
- **Problem** description
- **Required Fix / Required Change** (what needs to change)
- **Acceptance Criteria** (checkboxes)
- **Technical Notes** (implementation hints)
- **Progress Notes** (history of what was done, deployment notes)

## Assignment Field
- `Assigned` column in TRACKER.md tracks who is working on the item
- Set to agent name when work begins, `—` when unassigned
- Only one agent per item at a time

## Priority Levels
- **CORE**: Must work for core functionality. Highest priority.
- **HIGH**: Important but not blocking core flow.
- **MEDIUM**: Nice to have, quality improvement.
- **LOW**: Polish, minor issues.
- **INFRA**: Infrastructure/deployment issues.

## When Starting Work on an Item
1. Set status to `started` in both TRACKER.md and the item file
2. Set `Assigned` to your agent name in TRACKER.md
3. Read the full item file for requirements and acceptance criteria

## When Deploying
1. Set status to `untested` in both files
2. Add deployment notes to the item file under Progress Notes
3. Do NOT claim the work is "done" or "complete" — it is `untested` until user accepts

## Adding New Items
1. Create NNN.md with next sequential number
2. Add row to TRACKER.md index table
3. Include `**Previously**:` field if merging from older tracking IDs