todo

Manage private per-project todo backlogs stored outside the repository.

1|Updated Jun 17, 2026
One-click install
npx skills add https://github.com/Sfzmango/Maungs-agentic-toolbelt --skill todo-sfzmango
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: todo
Source: https://github.com/Sfzmango/Maungs-agentic-toolbelt/tree/main/plugins/maungs-agentic-toolbelt/skills/todo
Command: npx skills add https://github.com/Sfzmango/Maungs-agentic-toolbelt --skill todo-sfzmango

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill solves the issue of personal deferred work items either being accidentally committed to your project repository (creating public noise) or disappearing between coding sessions (if stored in ephemeral session memory), giving you a persistent, private scratchpad for tasks you want to table for later.

Core Features & Use Cases

  • Private Local Storage: All todo items are stored exclusively in a local file outside your project repository, so they never appear in issues, PRs, or shared project context.
  • Per-Project Scoping: The backlog is automatically tied to your current project via a unique slug derived from the git root, so todos from different codebases never mix.
  • Full Task Management: Add, complete, remove, and edit todo items with simple commands, with built-in confirmation prompts for destructive actions like deletion to prevent accidental data loss.
  • Use Case: Track deferred work like "revisit the caching strategy" or "add a README section for the new export flow" without creating public repo artifacts, and resume these tasks in future coding sessions.

Quick Start

To add a deferred task to your private per-project backlog, invoke the todo skill with the task text, for example by saying add rework the authentication flow to my backlog.

Frequently Asked Questions about todo

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I track private todo items for a specific project without committing them to git?

Private per-project todo items are tracked using local-only storage outside the repository. A unique slug derived from the git root scopes tasks to your current codebase, ensuring deferred work never appears in shared project artifacts.

What is the best way to manage deferred developer tasks across multiple coding sessions?

Deferred developer tasks are managed via a persistent local backlog that survives across coding sessions. You can add, edit, complete, and remove tabled items like documentation updates or strategy revisits without relying on ephemeral session memory.

Can I keep my local task backlog scoped per repository so todos from different codebases don't mix?

Yes, per-project scoping is automatically enforced by computing a unique slug from the git root. This ensures your local task backlog remains isolated to the specific repository you are working in.

Does this task-tracking approach require any external dependencies or shared project context?

No external dependencies or shared project context are required. The task-tracking backlog operates entirely on strict local-only storage, keeping your private tasks isolated from issues, PRs, and public repo artifacts.

How do I prevent accidental data loss when deleting or modifying my private task backlog?

Accidental data loss is prevented through explicit user-directed mutations and built-in confirmation prompts for destructive actions. The backlog enforces strict local-only storage to prevent unauthorized changes or accidental data leakage.

When should I not use a private local backlog for tracking deferred work?

A private local backlog should not be used for tasks requiring team visibility or shared project context. It enforces strict local-only storage and is explicitly designed to prevent deferred work items from surfacing in repository artifacts.