progress-tracking

Standardize multi-step agent procedures with a todo-first ledger convention.

8|1|Updated Mar 28, 2026
One-click install
npx skills add https://github.com/bostonaholic/team --skill progress-tracking-bostonaholic
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: progress-tracking
Source: https://github.com/bostonaholic/team/tree/main/skills/progress-tracking
Command: npx skills add https://github.com/bostonaholic/team --skill progress-tracking-bostonaholic

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill prevents task drift and silent step-skipping during complex, multi-step procedures by enforcing a standardized todo-list convention.

Core Features & Use Cases

  • Granular Tracking: Ensures every numbered step in a procedure is explicitly marked as in-progress or completed.
  • Context Isolation: Maintains separate ledgers for orchestrators and individual agents to prevent state pollution.
  • Use Case: When an agent is tasked with a complex refactoring job, it uses this convention to track its progress through each file and function modification, ensuring no part of the plan is overlooked.

Quick Start

Instruct the agent to initialize a progress ledger for the current multi-step procedure to ensure all tasks are tracked.

Frequently Asked Questions about progress-tracking

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

FAQPage Schema
How do I track progress in multi-step agent workflows?

Multi-step agent workflow progress tracking is standardized through a todo-first ledger convention, explicitly marking every numbered step as in-progress or completed to prevent task omission and drift.

Why does my agent skip steps during complex refactoring procedures?

Agents skip steps during complex procedures due to silent task drift, which a standardized todo-list convention prevents by enforcing granular, step-by-step progress monitoring across each modification.

How do I prevent state pollution between orchestrators and agents?

State pollution between orchestrators and agents is prevented by maintaining separate ledgers, enforcing an orchestrator-agent ledger separation contract to ensure strict context isolation and state integrity.

Do I need dependencies to implement progress tracking for agent procedures?

No dependencies are required to implement progress tracking for agent procedures, as the convention applies a standardized todo-first ledger approach directly within the workflow to maintain task visibility.

What's the best way to maintain visibility in complex agent tasks?

The best way to maintain visibility in complex agent tasks is implementing a standardized progress ledger, ensuring every numbered step is explicitly tracked to prevent silent step-skipping and task drift.