todo-tracker

Tracks durable work items across workstations and agents using git-backed context packs.

5|3|Updated Sep 9, 2026
One-click install
npx skills add https://github.com/SalesforceLabs/revenue-cloud-foundations --skill todo-tracker-salesforcelabs
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: todo-tracker
Source: https://github.com/SalesforceLabs/revenue-cloud-foundations/tree/main/.cursor/skills/todo-tracker
Command: npx skills add https://github.com/SalesforceLabs/revenue-cloud-foundations --skill todo-tracker-salesforcelabs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Session-based task lists disappear when a session ends, and parallel work across machines or agents silently duplicates effort. This Skill provides a durable, git-backed tracker for finding, claiming, and closing work items so ownership and progress survive across workstations, agents, and review rounds. ## Core Features & Use Cases - Durable context packs: Each work item is a pack capturing what done looks like, established facts with dates and evidence, rejected approaches, and verification steps. - Claim and closeout protocol: Claiming pushes to the remote so simultaneous starts collide instead of duplicating work; closing enforces acceptance gates and moves packs to done/. - Sequencing metadata: blocked_by/blocks express hard ordering while bundle groups items cheaper to do together. - Use Case: Starting a session cold, run the index list command to see every open pack with claim age and blockers, read a full pack, claim it, and retain ownership through PR review until agreed acceptance. ## Quick Start Ask the agent to list open work items with the todo tracker, show the details of one pack, and claim it before starting work.

Frequently Asked Questions about todo-tracker

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

FAQPage Schema
How do I track work items across multiple machines and agents?

Store each work item as a context pack in a git repository cloned to .agents/artifacts, then use index.py list, show, claim, and close to manage it. The push on claim makes simultaneous starts collide instead of duplicating work.

How do I claim a todo item before starting work?

Run python .agents/artifacts/todos/index.py claim <id>, which pulls, stamps, commits, and pushes in one step. It refuses an already-claimed pack and reports who holds it and since when.

What access is required to use this todo tracker?

It requires access to the private rlm-base-artifacts repository, cloned with git clone into .agents/artifacts. If the clone fails, the tracker is unavailable and you should continue without it rather than guessing its contents.

When should I release a claimed work item?

Release only when actually handing off, abandoning, or explicitly parking an item so someone else can take it. Ending a turn, finishing a review round, or waiting on merge approval is not a release event.

Why does index.py --check exit 1 even when nothing is wrong?

The index embeds computed claim ages, so time alone stales it and a stale index exits 1 exactly like a real closeout violation. Read the message: INDEX.md is stale means regenerate, while Closeout problems means fix the pack.