Todo management

**Quick judgment** Solid, well-scoped per-workspace todo manager with clear operational rules, good safety defaults, and minimal chat noise. Best suited for developer or project-centric environments where a simple, local, CLI-driven task list is enough. **Key strengths** - Uses a single, well-defined CLI (`scripts/todo.sh`) over SQLite, which should work reliably across most Unix-like dev environments. - Per-workspace `todo.db` (or overridable via `TODO_DB`) cleanly separates tasks by project. - Supports groups and explicit statuses (`pending`, `in_progress`, `done`, `skipped`), covering basic workflow needs. - Strong safety constraints: no arbitrary file writes, cautious handling of destructive actions, and explicit confirmation when deleting group entries. **Risks & limitations** - Functionality is intentionally narrow: no due dates, priorities, recurrence, or cross-workspace views. - Hard restriction on file creation/editing (no markdown exports, summaries to files, etc.) limits integration with note-taking or reporting workflows. - Ultra-short confirmations may feel terse or opaque in more conversational contexts, and users must explicitly ask to see their list. - Depends on the presence and correctness of `{baseDir}/scripts/todo.sh` and SQLite; misconfiguration there will break all operations. **Recommended scenarios** - Development teams or individual developers wanting a lightweight, repo-local task tracker managed through CLI and chat. - Workspaces where persistent state must stay local in a simple database, without external services. - Agents that frequently mutate tasks but should keep chat output minimal and focused. - Environments where safety around destructive actions and file I/O is important, and where users are comfortable occasionally specifying IDs for precise edits/removals.