todo-tracker

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

33|12|Updated Sep 24, 2024
One-click install
npx skills add https://github.com/bgaldino/rlm-base-dev --skill todo-tracker-bgaldino
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: todo-tracker
Source: https://github.com/bgaldino/rlm-base-dev/tree/main/.cursor/skills/todo-tracker
Command: npx skills add https://github.com/bgaldino/rlm-base-dev --skill todo-tracker-bgaldino

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/. - Index and validation tooling: The index.py tool lists, shows, claims, releases, and closes packs, and validates the tracker with --check. - Use Case: Starting a session cold with no idea what is in flight, you list open packs, read one fully, claim it (which pushes immediately), and keep the claim through implementation, CI, and review until agreed acceptance is met. ## Quick Start Ask the agent to list the open todo packs, show the details of one item, and claim it so the claim is pushed to the shared tracker.

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-backed artifacts repository cloned to .agents/artifacts. Claim items with index.py claim, which commits and pushes so the claim is visible on every workstation and simultaneous starts collide instead of duplicating work.

How do I claim a todo item without conflicting with someone else?

Run 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, so you pull, re-read the index, and pick something else.

What access is required to use this todo tracker?

It requires access to the private rlm-base-artifacts repository, cloned to .agents/artifacts. It is an optional maintainer workflow; public contributors do not need it and can follow the standard contributing guide instead.

When should I release a claimed work item?

Release only when actually handing off, abandoning, or explicitly parking an item so someone else may take it. Ending a turn, finishing a review pass, or waiting on merge approval is not a release event; keep the claim for the whole work item.

Why does index.py --check fail with a stale index message?

The index embeds computed claim ages, so time alone stales it and the check exits 1 roughly daily even when nothing changed. A stale index means regenerate it, while a closeout problems message means fix the pack itself.