Manages a persistent nested task queue in a single TODO.json file via a prebuilt binary.
npx skills add https://github.com/tschallacka/ai-skills --skill todo-tschallacka
Please help me install this Agent Skill. Skill: todo Source: https://github.com/tschallacka/ai-skills/tree/main/todo Command: npx skills add https://github.com/tschallacka/ai-skills --skill todo-tschallacka
todo command rather than hand-editing. - Enforced closure evidence: Closing a task as done, dropped, or obsolete without a note is refused, so every closed item records what happened. - Queue hygiene and safety: todo prune archives closed tasks to dated files while holding back anything an open task still depends on, todo check validates the register, and todo resolve handles merge conflicts over task ids. - Use Case: An agent juggling a multi-session refactor files each work item with todo add, checks todo report at the start of every session to see what is still open, and closes items with commit references as they land. ## Quick Start Ask the agent to register the current work items in the todo queue and show what is still open.High-intent search queries and answers about installing and using this skill.
Store tasks in a TODO.json file managed by the todo command instead of chat checklists. The file persists across restarts and handoffs, and todo report prints what is still open at the start of any new session.
Run todo add with --parent followed by the parent task id, along with the required --title and --detail flags. Sub-tasks carry their own priority and can be closed independently while sibling tasks remain open.
Use the register when work must outlive the conversation, span a restart or handoff, or when juggling three or more separate work items. Short checklists finished within one conversation and defects belong elsewhere, such as the bug-report skill.
The todo command refuses to set done, dropped, or obsolete without a --note explaining what happened. This guarantees every closed task carries evidence such as a commit, decision, or reason, so closures remain auditable later.
Yes, todo resolve reads both sides from the git index mid-conflict, reports colliding ids, and applies rename decisions you pass in one run. Nothing is written until you return the confirmation token it prints.
todo prune moves closed tasks into a dated TODO.<date>.archive.json file, which remains a readable queue itself. Tasks still referenced by open work through parent or blocked_on links are kept back automatically.
pnewsamDecompose an initiative into independently reviewable work units with dependencies and integration proof.
semicolon-devteamUpdate GitHub issue status and request PO review after implementation.
NealschRecords, triages, tracks, and verifies defects through the software development lifecycle.
agentscope-aiGenerate ordered step-by-step execution plans with dependencies and verification points.