the-capo

Dispatch workers to complete Work Packages within a defined territory.

71|9|Updated Apr 13, 2026

Search Tags:#subagents #dispatch #work-packages #orchestrate #status-reporting #territory #contract-compliance

Ready to run

npx skills add https://github.com/kucherenko/gangsta --skill the-capo

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: the-capo
Source: https://github.com/kucherenko/gangsta/tree/main/skills/the-capo
Command: npx skills add https://github.com/kucherenko/gangsta --skill the-capo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Capo skill orchestrates a territory-specific crew, dispatching workers to complete Work Packages while ensuring alignment with the contract and transparent status reporting to the Underboss.

Core Features & Use Cases

Territory-bound orchestration: define a domain and dispatch workers within a bounded codebase territory.
Worker briefing and reporting: generate briefs, collect reports, and validate against contract clauses.
Status tracking and governance: provide ongoing status updates and audit-ready documentation.

Quick Start

Define a Territory and Work Packages, then instruct the Capo to dispatch soldiers and report WP outcomes.

Frequently Asked Questions about the-capo

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

FAQPage Schema

How do I orchestrate subagents to complete work packages in a specific codebase territory?▼

Subagent dispatch for software projects works by planning workers to execute bounded work packages, validating their reports against contract compliance clauses, and tracking status across multiple cycles to ensure transparent outcomes.

Can I enforce contract compliance and audit trails when dispatching workers to subagents?▼

Yes, you can enforce contract compliance by validating worker reports against contract clauses, generating audit-ready documentation, and maintaining ongoing status tracking across multiple work package cycles.

What is the best way to track status across multiple work package cycles in software engineering?▼

Tracking status across multiple work package cycles requires dispatching workers within a bounded domain, collecting their reports, and validating outcomes against contract clauses to provide transparent updates and audit-ready documentation.

Does this territory orchestration approach work without external dependencies?▼

Yes, territory orchestration works without external dependencies, relying entirely on internal worker dispatch protocols, status reporting mechanisms, and contract compliance validation to manage work packages.

When do I need bounded territory orchestration for software project work packages?▼

You need bounded territory orchestration when managing domain-specific software projects that require planning worker dispatch for work packages, ensuring contract compliance, and maintaining clear acceptance criteria with audit trails.