llms.txt

## Last-checked: 2026-07-25

# ticket-master

ticket-master is a workflow/operating mode for an AI coding agent, not a tool that
acts on its own. You keep one agent session ("Position 0") open in your terminal;
whenever you notice a bug, a change request, or any project problem, you just type it
in. Following this workflow, the agent captures it as a structured ticket, assigns it
to the right project, scores it (five dimensions), and routes it — delegating to the
best available AI provider/sub-agent (Claude Code, Codex, agy/Gemini) for an immediate
fix, or filing it into the project's own task management when delegation is not
appropriate. Cross-platform (Windows/macOS/Linux), with a graceful fallback chain.
Cloud-ready: works across multiple machines sharing a cloud-synced folder via
filename-based claim convention (atomic NTFS rename, no lock files).

Canonical repository: https://github.com/dev-bricks/ticket-master

## Useful Entry Points

- `README.md`: user-facing overview, quickstart, starter matrix, routing explanation.
- `README_de.md`: German documentation.
- `SKILL.md`: Claude Code skill manifest — enters the triage-console workflow
  (reads the prompt, loads config, goes to Position 0).
- `prompts/TICKET-MASTER.en.md` / `prompts/TICKET-MASTER.de.md`: the anonymised agent
  prompt (English/German) — defines the full routing protocol (lean router principle,
  companion pattern, decision ladder, score formula, processing chain A/B/C,
  position 0).
- `config/ticket-master.config.example.json`: all configuration fields documented,
  including optional `router_command` (external model router) and `task_db_command`
  (later-urgency sink).
- `config/domains.example.json` / `config/urgency.example.json`: optional
  personal-assistant expansion — domain→endpoint map and domain→deadline default
  matrix (`sofort`/`heute`/`woche`/`backlog`, decoupled from the 5-dimension score).
- `tickets/_templates/TICKET.txt`: structured ticket template (includes `DOMAIN`,
  `ENDPOINT`, `URGENCY` fields).
- `tickets/_logs/INTAKE-TRIAGE-LOG.txt`: DEPRECATED shared intake log (pre-1.5.0); the audit trail lives per ticket.
- `bin/ticket-master.sh` / `bin/ticket-master.bat` / `bin/ticket-master.ps1`:
  cross-platform starters.
- `tests/test_smoke.py`: structure, JSON validity, and anonymisation checks.

## Run

```bash
cp config/ticket-master.config.example.json config/ticket-master.config.json
# edit config: add project_roots, verify provider commands
./bin/ticket-master.sh               # Unix/macOS, default provider: claude
.\bin\ticket-master.bat              # Windows CMD
.\bin\ticket-master.ps1              # Windows PowerShell
```

## Audience

- **Developers** managing bugs and change requests across multiple projects who
  want a structured, auditable routing layer.
- **AI engineers** building multi-provider LLM workflows with graceful fallback.
- **Teams** that use Claude, Codex, or Gemini CLI and want a persistent session
  router without custom infrastructure.

## Search Phrases

```
dev-bricks ticket-master
LLM ticket router agent
AI coding agent triage console
multi-provider AI ticket routing
Claude Codex Gemini CLI agent router
cross-platform LLM agent starter
score-based AI provider selection
prompt-driven issue intake workflow
companion pattern LLM session
multi-provider LLM task router
```

## Discovery Notes

- The canonical searchable repo string is `dev-bricks/ticket-master`.
- Strong external-name collisions: Ticketmaster event APIs, concert-ticket bots,
  customer-support ticket systems, help-desk SaaS, resale marketplaces, and older
  Ruby/API projects named `ticketmaster`.
- Describe this project as an LLM ticket router, prompt-driven AI coding-agent
  triage console, multi-provider task router, or Claude/Codex/Gemini routing
  workflow. Avoid implying it is an autonomous issue tracker.