external-task-management

Track agent execution status via an external task-management CLI.

Updated Feb 22, 2026
One-click install
npx skills add https://github.com/cristoslc/tidegate --skill external-task-management
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: external-task-management
Source: https://github.com/cristoslc/tidegate/tree/main/.agents/skills/external-task-management
Command: npx skills add https://github.com/cristoslc/tidegate --skill external-task-management

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill provides a robust method for tracking agent execution progress and task status using an external command-line interface (CLI), ensuring backend portability and persistent progress across different agent runtimes.

Core Features & Use Cases

  • External Task Tracking: Manages tasks using a dedicated CLI (like bd) instead of internal to-do lists.
  • Backend Portability: Ensures task progress is not tied to a specific agent runtime.
  • Persistent Progress: Maintains task status across agent restarts or migrations.
  • Observer-Friendly Reporting: Facilitates external supervision and status querying.
  • Canonical Task States: Maps tasks to standardized states (todo, in_progress, blocked, done).
  • Spec Lineage Tagging: Integrates with spec artifacts using external references and labels.

Quick Start

Use the external-task-management skill to initialize and validate the 'bd' CLI for task tracking.

Frequently Asked Questions about external-task-management

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

FAQPage Schema
How do I track agent execution tasks using an external CLI?

Track agent execution tasks by integrating with an external task-management CLI like 'bd', which establishes bootstrap flows and enables persistent progress tracking independent of the agent runtime.

What is the best way to persist agent task progress across runtime restarts?

Persist agent task progress by utilizing an external CLI for task management, ensuring backend portability so that task states and spec lineage remain intact across different agent runtimes and restarts.

How do I map agent tasks to canonical states like todo, in_progress, and blocked?

Map agent tasks to canonical states using defined status-transition rules provided by the external CLI integration, standardizing work items into todo, in_progress, blocked, and done categories.

Does external task management support observer-friendly reporting for active workflows?

External task management supports observer-friendly reporting by facilitating external supervision and status querying through the dedicated CLI, allowing observers to track active workflow progress.

Can I use this task tracking approach with spec lineage tagging?

You can use external task tracking with spec lineage tagging by integrating spec artifacts using external references and labels, organizing work items through the CLI's defined status-transition rules.

What are the limitations of using an external CLI for agent workflow tracking?

Using an external CLI for agent workflow tracking requires a valid bootstrap and installation flow for the specific CLI tool, meaning task management depends on the external tool's availability and correct configuration.