local-task-tracker

name	local-task-tracker
description	Work item status management rules and tracker structure for FlowMaster runs
disable-model-invocation	true

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