Progress tracking

Skill bostonaholic/team/skills/progress-tracking

Drive a feature from idea to PR with a team of Claude Code agents.

Install

npx -y skills add bostonaholic/team --skill progress-tracking

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

8 stars8 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Todo-first progress convention for multi-step procedures — loaded by every multi-step agent to track its own steps without drift

SKILL.md

1.5 KB, as published. Nobody here has run it

Progress Tracking

A convention, not a gate. It produces no artifact and blocks nothing. It shapes how any agent or skill executing a multi-step procedure keeps its own work visible, so steps are not silently skipped.

When it applies

When a procedure has two or more ordered steps, seed one todo item per step before starting and mark each complete as you go. A single-step procedure is exempt — a one-item ledger is noise.

Per-step granularity

One todo item per numbered step — not per phase, not per file. Mark each item in_progress when its step starts and completed when that step lands, matching how team-fix already marks each step. Keep items at the granularity of the procedure's own numbered list.

Ledger ownership

The orchestrator (the main Claude Code session) owns the single phase-level ledger. An agent executing a multi-step skill tracks its own sub-steps within its own context and never merges them up into the orchestrator's phase ledger. A standalone, directly-invoked skill seeds its own ledger. The two ledgers live in separate ownership scopes and are never read across.