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 Intent | Action | Skill Invoked |
|---|---|---|
| Build something new | Start a Heist | gangsta:reconnaissance |
| Fix a bug or issue | Get diagnosis first | gangsta:the-consigliere |
| Debug a problem | Systematic root-cause analysis | gangsta:interrogation-debugging |
| Continue existing work | Resume from checkpoint | Check docs/gangsta/ for files |
| Ask a question | Answer directly | No skill needed |
| Review or audit | Structured assessment | gangsta:audit-review |
| Write tests first | TDD cycle | gangsta:drill-tdd |
| Process feedback | Rigorous review | gangsta:receiving-orders |
Skill Priority
When multiple skills could apply, routing follows this order:
- Process skills first —
reconnaissance,interrogation-debugging,drill-tdd- These determine how to approach the task
- They set up the methodology before any work begins
- Orchestration skills second —
the-underboss,the-capo- These manage who does what
- They decompose work after the approach is established
- Implementation skills third —
the-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 shortcutsgangsta:interrogation-debugging— Systematic root-cause, no guessinggangsta: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 sizegangsta:the-grilling— Debate depth adapts to feature complexity
Common Routing Mistakes
Anti-patterns to avoid:
- Skipping reconnaissance — "I already know the codebase" → You probably don't know it as well as a systematic scan. Invoke
gangsta:reconnaissance. - Debugging without structure — "Let me just try changing this line" → Use
gangsta:interrogation-debuggingfor systematic root-cause analysis. - Coding without a spec — "I'll just start implementing" → This violates Omerta Law #5 (Spec is Law). Run a Heist first.
- 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.