task-ledger-mcp

Manage mutable task state through explicit MCP operations in a ledger.

Updated Apr 1, 2026
One-click install
npx skills add https://github.com/lilmuckers/agentic-team-plugin --skill task-ledger-mcp
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: task-ledger-mcp
Source: https://github.com/lilmuckers/agentic-team-plugin/tree/main/skills/task-ledger-mcp
Command: npx skills add https://github.com/lilmuckers/agentic-team-plugin --skill task-ledger-mcp

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The MCP ledger provides a single source of truth for mutable task state and prevents ad hoc markdown, chat, or scattered surfaces from diverging task data.

Core Features & Use Cases

  • Centralized task state management via the MCP ledger with explicit mutations.
  • Supports creating, updating, transitioning, invalidating tasks, adding notes, and linking artifacts.
  • Read-only surfaces for querying task history, project metadata, and task state progression across roles (Orchestrator, Spec, Builder, QA, Security, Release Manager).

Quick Start

Create a new task with a title and project_id, then transition it through its lifecycle using the MCP task APIs.

Frequently Asked Questions about task-ledger-mcp

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

FAQPage Schema
How do I centralize mutable task state management to prevent scattered markdown and chat from diverging?

Centralized task state management uses an MCP ledger to maintain a single source of truth for tasks. It enforces mutations through explicit operations, preventing ad hoc markdown or chat surfaces from diverging task data.

What is the best way to transition task states across orchestrator, builder, and QA roles?

Transitioning task states across roles uses the task_transition MCP operation within the ledger. This ensures all orchestrator, spec, builder, QA, security, and release manager roles mutate task state through a canonical interface.

Can I link artifacts and add notes to task history using a task ledger?

Linking artifacts and adding notes to task history uses the task_link_artifact and task_add_note MCP operations. These explicit mutations ensure all artifact links and notes are permanently tracked within the centralized ledger.

How do I query task history and project metadata without mutating the task state?

Querying task history and project metadata uses the read-only surfaces provided by the MCP ledger. These surfaces allow you to retrieve task state progression and project details without risking accidental mutations to the task data.

When should I invalidate a task in an end-to-end workflow?

Invalidating a task in an end-to-end workflow uses the task_invalidate MCP operation when a task becomes obsolete or blocked. This explicitly removes it from active task state progression within the ledger.