work-queue

To organize cross-platform work items, you create a .agent/queue/ directory and add standardized work-item files to track status, priority, and assignees for each task. This local queue structure allows you to break down large tasks into smaller, trackable items.

The best way to track task status and priority is by using a standardized work-item format within a local queue. You create files like 001-pending-setup-queue.md in the .agent/queue/ directory to monitor and report remaining work across your project.

To create a work item file for task management, you generate a markdown file inside the .agent/queue/ directory using a standardized naming convention like 001-pending-setup-queue.md. This file must contain the required structure to track the task's status and priority.

Yes, you can use a local queue to break down large tasks into smaller trackable items. This skill helps teams manage large tasks by creating a dedicated .agent/queue/ directory to organize, update, and list individual work items.

No, you do not need any external dependencies to monitor progress across a work queue. The system operates locally by applying standardized work-item formats and commands to add, update, and list tasks in the .agent/queue/ directory without dependencies.

You use a standardized work-item format for cross-platform task tracking to ensure consistent status, priority, and assignee monitoring across different environments. By maintaining standardized markdown files in a local queue, you can reliably list remaining or in-progress tasks.