tasks

Aggregate task statuses from multiple repositories and flag inactive tasks.

Updated May 7, 2026
One-click install
npx skills add https://github.com/ChazzCoin/claude-orchestrator --skill tasks-chazzcoin
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: tasks
Source: https://github.com/ChazzCoin/claude-orchestrator/tree/main/kit/skills/tasks
Command: npx skills add https://github.com/ChazzCoin/claude-orchestrator --skill tasks-chazzcoin

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill provides a consolidated view of the active tasks across multiple projects, ensuring that team members have a single source of truth about the ongoing work.

Core Features & Use Cases

  • Cross-repo Task Aggregation: Combines task statuses from all registered sub-repositories into one document.
  • Task Stale Flagging: Identifies and flags tasks that have been inactive for an extended period.
  • Output Pattern: Generates a sprint task board-like output and a concise chat summary for easy reference.
  • Use Case: A team leader can quickly understand the current status of tasks across various projects without manually checking each repository.

Quick Start

Run the "/tasks" command to generate a comprehensive overview of active tasks.

Frequently Asked Questions about tasks

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

FAQPage Schema
How do I track active tasks across multiple repositories for sprint planning?

Aggregating task information from multiple repositories into a unified view allows you to track active tasks for sprint planning. It combines statuses from all registered sub-repositories into one document, serving as a single source of truth.

What is the best way to identify stale tasks in cross-repo project coordination?

The best way to identify stale tasks in cross-repo project coordination is by using a task aggregation mechanism that automatically flags inactive tasks. It scans all registered sub-repositories to highlight work that has not been updated for an extended period.

Does cross-repo task aggregation work with non-kit repositories?

Yes, cross-repo task aggregation works with non-kit repositories. The system reads repository configurations and is specifically designed to handle both kit-enabled and non-kit repositories to ensure comprehensive task tracking.

How do I generate a sprint task board and chat summary from work status data?

You can generate a sprint task board and chat summary from work status data by running a single command that processes aggregated cross-repo task information. It outputs a board-like document and a concise summary for quick team reference.

When do I need a unified task view for team coordination?

You need a unified task view for team coordination when managing multiple projects simultaneously and requiring a single source of truth. It prevents team members from manually checking each individual repository to understand the current work status.