Set up Anthropic Task Management safely

What the Task Management skill is

The Task Management skill comes from Anthropic's official knowledge-work-plugins repository and belongs to a collection of productivity-oriented skills for AI assistants such as Claude. A skill, in this context, is a retrievable set of instructions that tells an AI model how to consistently handle a specific, recurring task without requiring fresh instructions every time. According to the provider, the Task Management skill keeps tasks in a simple, human-readable file called TASKS.md that both the assistant and the person using it can edit directly. Per its description, the skill is invoked whenever someone asks about open tasks, wants to add or complete a task, or needs help tracking commitments.

Structure of TASKS.md and how it works

The skill specifies that the TASKS.md file always lives in the current working directory. If the file already exists, the assistant reads and writes directly to it; if it doesn't, a new one is created from a fixed template. That template defines four sections: Active tasks, tasks the user is Waiting On, tasks for Someday, and Done tasks. Each task is recorded as a checkbox line with a highlighted title, optionally followed by context such as who is responsible or a due date, with sub-bullets available for further detail. Completed tasks get struck through and dated before moving into the Done section, which, per the stated convention, is cleared out after roughly a week to keep the file manageable.

Interaction and the optional dashboard

When someone asks what's on their plate, the assistant reads the file and summarizes the Active and Waiting On sections, calling out anything overdue or urgent. When someone mentions a new task, the assistant appends it to the Active section along with any available context. When someone reports finishing something, the assistant locates the matching entry, marks it done, and moves it into the Done section with a date. The repository also describes an optional visual dashboard delivered as an HTML file, which can be copied into the working directory the first time the task system is used. That dashboard reads and writes the same TASKS.md file, auto-saves changes, detects edits made externally via the command line, and supports drag-and-drop reordering of tasks and sections.

Practical value, limits, and safety

The main appeal of this approach is its simplicity: because everything lives in a single plain-text Markdown file, it can be opened with any ordinary editor, checked into version control, or processed by other tools without needing a separate database or cloud service. At the same time, that also means the skill offers no reminders, notifications, or multi-device, multi-user synchronization; it is designed as a lightweight, local tool rather than a full project management system. When extracting tasks from meeting notes or conversations, the stated convention requires the assistant to ask before adding entries rather than adding them automatically, which prevents unwanted or misattributed tasks from cluttering the list. Anyone who records sensitive details, such as client names or internal project information, inside TASKS.md should keep in mind that the file is treated like any other local text file and should be protected with the same access controls and backup practices as the rest of the project directory.