Agent Coordination with dex
Command Invocation
Use dex directly for all commands. If not on PATH, use npx @zeeg/dex instead.
command -v dex &>/dev/null && echo "use: dex" || echo "use: npx @zeeg/dex"
Core Principle: Tickets, Not Todos
Dex tasks are tickets - structured artifacts with comprehensive context:
Name: One-line summary (issue title)
Description: Full background, requirements, approach (issue body)
Result: Implementation details, decisions, outcomes (PR description)
Think: "Would someone understand the what, why, and how from this task alone?"
related skills
semantically similar in the cross-vendor index
don't have the plugin yet? install it then click "run inline in claude" again.
+emphasizes tickets as first-class objects with explicit name/description/result fields, forcing upfront context capture
+recognizes this targets persistent session context, not ephemeral lists, which is a real use case gap
weaknesses
~zero procedure specificity: no examples of dex create, dex list, dex update commands or their actual outputs
~no edge cases acknowledged (what if ticket exists, sync conflicts, data loss, malformed input). does dex handle concurrent writes?
~trigger phrases absent entirely. when would a user invoke this vs a note app or issue tracker?
~installation check shown but no guidance on failures, no troubleshooting for unmet nodejs/npm versions