kucherenko/gangsta

reconnaissance

Use when beginning a new heist — deploys associates to survey the target codebase, existing tests, dependencies, documentation, and the ledger to produce a reconnaissance dossier for the don's review

原文の言語: 英語

the-sit-down

Use when the grilling consensus is approved and it is time to draft the formal contract specification — strictly prohibits code generation, produces the binding spec document that governs all subsequent phases

原文の言語: 英語

using-gangsta

Use when starting any conversation — establishes how to find and use Gangsta skills, enforces the 1% invocation rule, maps platform tools, and routes the Don's intent through the Gangsta Agents Family hierarchy

原文の言語: 英語

laundering

Use when all territories report completion after the hit — handles integration, verification, consigliere final review, cleanup, and ledger updates to produce clean production-ready code

原文の言語: 英語

the-hit

Use when the execution plan is approved and it is time for parallel execution — dispatches workers through crew leads to implement work packages with TDD enforcement, report collection, and escalation protocols

原文の言語: 英語

omerta

Use when enforcing governance guardrails during any gangsta operation — referenced as cross-cutting concern by all skills for anti-hallucination, authorization, state durability, resource management, and spec supremacy rules

原文の言語: 英語

resource-development

Use when the contract is signed and work packages need to be created — decomposes the contract into bite-sized tasks, sets up git isolation, allocates territories and token budgets, producing the execution plan

原文の言語: 英語

the-grilling

Use when adversarial brainstorming is needed after reconnaissance — the Proposer, Devils-Advocate, and Synthesizer each run ONE pass (no rounds); the Don is grilled on the IDEA first, one question at a time, then the proposal is attacked

原文の言語: 英語

the-underboss

Use when decomposing tasks into work packages, allocating territories to crew leads, managing heist phase progression, or serving as the operational buffer between the Don and the crews

原文の言語: 英語

receiving-orders

Use when receiving code review feedback — processes orders with technical rigor, not blind obedience or performative agreement

原文の言語: 英語

safehouse-worktrees

Use when starting feature work that needs isolation from the current workspace — sets up a secure safehouse with git worktrees for clean operational bases

原文の言語: 英語

audit-review

Use when completing tasks, implementing major features, or before merging — dispatches the-inspector to audit the books before the job is closed

原文の言語: 英語

interrogation-debugging

Use when encountering any bug, test failure, or unexpected behavior — finds the rat in the code through systematic root-cause interrogation before any fix attempts

原文の言語: 英語

sweep-verification

Use when about to claim work is complete, fixed, or passing — sweeps for evidence before any assertions, because unverified claims are invalid

原文の言語: 英語

the-capo

Use when orchestrating workers within a specific domain territory — managing work package dispatch, reviewing reports against the contract, and reporting status to the underboss

原文の言語: 英語

the-consigliere

Use when needing impartial architectural advice, security audit, spec integrity review, or a second opinion — operates outside the chain of command with standing authority to invoke truth checks

原文の言語: 英語

the-ledger

Use when reading or writing institutional memory — insights from successful solutions, fails from historical mistakes, and the Project Constitution that accumulates commandments and negative constraints across heists

原文の言語: 英語

exit-strategy

Use when implementation is complete and all tests pass — guides the clean exit from a development branch with structured options for merge, PR, or cleanup

原文の言語: 英語

drill-tdd

Use when implementing any feature or bugfix — enforces the Red-Green-Refactor drill with no production code allowed without a failing test first

原文の言語: 英語