Core Concepts

Intent Routing

How Gangsta maps user intent to the right skill invocation.

Intent Routing

When you speak, the agent analyzes your intent and routes it to the appropriate Gangsta skill. This routing is automatic — powered by the 1% Rule — but understanding the mapping helps you work more effectively.

Intent → Skill Mapping

User IntentActionSkill Invoked
Build something newStart a Heistgangsta:reconnaissance
Fix a bug or issueGet diagnosis firstgangsta:the-consigliere
Debug a problemSystematic root-cause analysisgangsta:interrogation-debugging
Continue existing workResume from checkpointCheck docs/gangsta/ for files
Ask a questionAnswer directlyNo skill needed
Review or auditStructured assessmentgangsta:audit-review
Write tests firstTDD cyclegangsta:drill-tdd
Process feedbackRigorous reviewgangsta:receiving-orders

Skill Priority

When multiple skills could apply, routing follows this order:

  1. Process skills firstreconnaissance, interrogation-debugging, drill-tdd
    • These determine how to approach the task
    • They set up the methodology before any work begins
  2. Orchestration skills secondthe-underboss, the-capo
    • These manage who does what
    • They decompose work after the approach is established
  3. Implementation skills thirdthe-hit, resource-development
    • These guide execution
    • They operate within the structure established by process skills

Skill Types

Skills come in two flavors:

Rigid Skills

Must be followed exactly. Don't adapt away from the discipline.

  • gangsta:drill-tdd — Red-Green-Refactor, no shortcuts
  • gangsta:interrogation-debugging — Systematic root-cause, no guessing
  • gangsta:omerta — Laws apply always, no exceptions

Flexible Skills

Adapt principles to context. The spirit matters more than the letter.

  • gangsta:reconnaissance — Intel gathering adapts to codebase size
  • gangsta:the-grilling — Debate depth adapts to feature complexity

Common Routing Mistakes

Anti-patterns to avoid:
  1. Skipping reconnaissance — "I already know the codebase" → You probably don't know it as well as a systematic scan. Invoke gangsta:reconnaissance.
  2. Debugging without structure — "Let me just try changing this line" → Use gangsta:interrogation-debugging for systematic root-cause analysis.
  3. Coding without a spec — "I'll just start implementing" → This violates Omerta Law #5 (Spec is Law). Run a Heist first.
  4. Auto-advancing phases — "The dossier looks fine, let's keep going" → Every phase gate requires explicit Don approval. No auto-advancing.

The Flow in Practice

User says "I want to add notifications"
  └── Intent: Build something new
       └── Skill: gangsta:reconnaissance
            └── Don approves Dossier
                 └── gangsta:the-grilling
                      └── Don approves Consensus
                           └── gangsta:the-sit-down
                                └── Don signs Contract
                                     └── gangsta:resource-development
                                          └── Don approves War Plan
                                               └── gangsta:the-hit
                                                    └── Don approves Completion
                                                         └── gangsta:laundering
                                                              └── Don declares Complete

Each arrow represents a phase gate — a point where you must explicitly approve before proceeding.

Copyright © 2026