dex

# Agent Coordination with dex

## Command Invocation

Use the bundled `./dex` script in this skill directory to run dex commands:

```bash
./dex <command>
```

The script automatically finds a local `dex` installation or falls back to `npx @zeeg/dex`.

Use dex to act as a **master coordinator** for complex work:
- Break down large tasks into structured deliverables
- Track tickets with full context (like GitHub Issues)
- Record implementation results (like PR descriptions)
- Enable seamless handoffs between sessions and agents

## Core Principle: Tickets, Not Todos

Dex tasks are **tickets** - structured artifacts with comprehensive context:
- **Description**: One-line summary (issue title)
- **Context**: Full background, requirements, approach (issue body)
- **Result**: Implementation details, decisions, outcomes (PR description)

This rich context enables:
- You (the agent) to resume work without losing context
- Other agents to pick up related work
- Coordinated decomposition of complex tasks
- Reconciliation of decisions and data across sessions

Think: "Would someone understand the what, why, and how from this task alone?"

## Important: Dex Tasks are Ephemeral

**Never reference Dex task IDs in external artifacts:**
- Commit messages
- Pull request descriptions
- GitHub issues
- Documentation

Dex tasks are temporary coordination tools, not permanent records. Task IDs like `abc123` will become meaningless once tasks are completed and cleaned up, and referencing them pollutes version history with dead links.

When creating commits or PRs, describe the work itself - not the dex task that tracked it.

## When to Use dex as Coordinator

Use dex when you need to:
- **Break down complexity**: Large feature → subtasks with clear boundaries
- **Track multi-step work**: Implementation spanning 3+ distinct steps
- **Persist context**: Work continuing across sessions
- **Coordinate with other agents**: Shared understanding of goals/progress
- **Record decisions**: Captur