XiaoyaoClaw Task Progress Tracker
Lightweight progress-card system over your workspace tasks/ and projects/ dirs — folders as containers, PROGRESS.md as progress, pure files, zero deps.
Product Introduction
OpenClaw Task Progress Tracker fixes four progress-management pains: half-done tasks lose context between sessions, reports end up in random folders, last week’s work can’t be traced, and heavyweight PM suites (CLI + external services) are overkill for file-based workflows. The solution: directories as containers + PROGRESS.md progress cards + doc index. tasks/<slug>/ (half-day to one-week tasks) and projects/<slug>/ (long-term maintenance) ARE the containers. Each PROGRESS.md card = frontmatter (status/progress/docs) + append-only log + doc index, both machine-readable (YAML docs[]) and human-readable (table). It’s disciplined — only acts on explicit commands, no global hooks (lesson from v1 noise). Pure files, no CLI, no external service, no DB. Plays well with the initializer and memory-distill.
Core Features
- Two-object model — tasks (half-day to weekly) + projects (long-term)
- Folders as containers — tasks/<slug>/ and projects/<slug/> ARE the entities
- PROGRESS.md cards — frontmatter (status/progress/docs) + append-only log + doc index
- Dual-channel doc index — YAML for machines, table for humans
- Disciplined — explicit commands only, no global hooks (lesson from v1)
- Zero deps — pure files, no CLI, no service, no DB
- Plays well with siblings — initializer + memory-distill
- Plain-language ops — open a task / start a project / say the progress / attach a doc