Task Tracker

**Judgment:** A solid, focused task-management skill that is well-suited for users who want structured daily standups and weekly reviews around a markdown-backed task file. It appears mature enough for regular work use, especially for individual contributors or small teams using the same environment. **Strengths:** - Good coverage of core task flows: list, add, complete, blockers, due dates, daily standup, weekly review, archiving. - Human-friendly, readable TASKS.md format that’s easy to inspect or edit by hand and works well with git or note-taking tools. - Natural language trigger patterns match common user phrasing ("daily standup", "what’s on my plate?", "what’s due this week?", etc.). - Task extraction from meeting notes reduces friction when turning notes into actionable items. **Key Risks / Limitations:** - Parsing logic depends on TASKS.md retaining the expected structure (headings, checkbox format, priority sections); manual edits that diverge may break behavior. - No evident support for complex multi-user or multi-project setups beyond simple owner/blocker fields; best as a personal or small-scope tracker. - Error handling and edge cases (corrupt files, unusual date formats, very large task sets) are only partially described; some reliability risk in less typical setups. **Recommended Scenarios:** - Users explicitly asking for "daily standup" or "weekly review" style summaries tied to persistent work tasks. - People who already keep or want to keep a markdown-based task list under `~/clawd/memory/work/` and are comfortable with simple CLI commands. - Situations where the assistant should extract structured tasks from meeting notes and convert them into actionable items with priorities and due dates. - Users asking what’s on their plate, what’s due this week/today, or what’s blocking specific collaborators, within a relatively small task set.