amcos-progress-tracking

Capture and synchronize task progress, dependencies, and recovery notes for per-team AMCOS contexts.

1|Updated Feb 27, 2026
One-click install
npx skills add https://github.com/Emasoft/ai-maestro-chief-of-staff --skill amcos-progress-tracking
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: amcos-progress-tracking
Source: https://github.com/Emasoft/ai-maestro-chief-of-staff/tree/main/skills/amcos-progress-tracking
Command: npx skills add https://github.com/Emasoft/ai-maestro-chief-of-staff --skill amcos-progress-tracking

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This skill captures and synchronizes task progress, dependencies, and recovery notes for per-team AMCOS contexts, ensuring continuity across sessions and agents.

Core Features & Use Cases

  • Centralized progress tracking for teams and multi-agent work
  • Dependency management and blocker handling
  • Snapshot-based recovery to guard against context loss
  • Examples include per-team task lifecycles, recovery after interruptions

Quick Start

Edit the Progress Tracker file at .session_memory/progress_tracker.md to record tasks, start/complete states, and dependencies, then use the references to manage patterns and snapshots before compaction.

Frequently Asked Questions about amcos-progress-tracking

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

FAQPage Schema
How do I track task progress and dependencies across multiple agents?

Snapshot-based recovery records task states and dependencies before compaction, allowing you to restore full context and resume work safely after interruptions or context window limits are hit.

How do I set up progress tracking for a per-team task lifecycle?

Blocker handling in multi-task work isolates unresolved dependencies within the progress tracker, preventing blocked tasks from cascading failures across the team's synchronized workflow.

Can I enforce consistent progress updates and safe rollback paths across agents?

AMCOS progress tracking is designed for per-team lifecycles involving multi-task work, blockers, compaction, and context recoveries, making it suited for complex multi-agent software engineering projects.

What's the best way to manage context recovery before compaction in multi-agent workflows?

Context recovery in this workflow relies on structured memory files and snapshots to capture task progress and dependencies, preventing context loss across sessions and agents.