the-hit

Dispatch crews through leads to execute work packages in parallel with TDD enforcement.

71|9|Updated Apr 13, 2026

Search Tags:#tdd #reporting #parallel #execution #work-packages #crew-leads

Ready to run

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

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Coordinate the parallel execution of work packages by dispatching crews through leads and enforcing TDD across all workers as soon as the Execution Plan is approved. Ensure structured reporting and escalation are in place to preserve contract alignment and governance.

Core Features & Use Cases

Parallel execution orchestration: dispatches workers through Crew Leads to implement Work Packages concurrently.
TDD enforcement: ensure Red-Green-Refactor cycles with mandatory tests before implementation.
Report collection and status rollups: structured Reports per Work Package with status and test results.
Escalation and governance: escalation paths from Workers to Crew Leads to Underboss and Don.
Autonomous-mode compatibility: operate with minimum Don intervention via a don-proxy in advanced setups.

Quick Start

Invoke gangsta:the-hit after the Execution Plan is approved to begin parallel implementation and reporting.

Frequently Asked Questions about the-hit

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

FAQPage Schema

How do I coordinate parallel execution of work packages while enforcing TDD?▼

Parallel execution of work packages is coordinated by dispatching crews through Crew Leads, enforcing strict Red-Green-Refactor TDD cycles across all workers once the Execution Plan is approved. This ensures structured reporting and governance during concurrent task implementation.

What is territory-based execution for parallel work packages?▼

Territory-based execution is an orchestration model that handles multiple Work Packages in parallel using Crew Leads and Worker subagents. It enforces contract-aligned task execution, rigorous reporting, and defined escalation paths from Workers to Crew Leads to Underboss and Don.

When do I need strict TDD enforcement across parallel development crews?▼

Strict TDD enforcement across parallel crews is needed when executing multiple Work Packages concurrently and you must ensure mandatory tests are written before implementation. It preserves contract alignment and governance through structured status rollups and test results reporting.

Does parallel work package execution support autonomous mode with minimal oversight?▼

Yes, parallel work package execution supports autonomous-mode compatibility by operating with minimum Don intervention via a don-proxy in advanced setups. This allows Crew Leads and Workers to maintain TDD enforcement and structured reporting without continuous manual oversight.

Can I use Crew Leads and Worker subagents for parallel implementation under defined constraints?▼

Yes, you can use Crew Leads to dispatch Worker subagents for parallel implementation of Work Packages under defined constraints. The system handles multiple packages concurrently, ensuring contract-aligned execution, mandatory TDD cycles, and structured escalation paths.

What's the best way to handle escalation paths during parallel TDD execution?▼

The best way to handle escalation during parallel TDD execution is through a structured governance model routing issues from Workers to Crew Leads, then to Underboss and Don. This ensures contract alignment and structured reporting are maintained across all concurrent Work Packages.