dex

Organize multi-session work as persistent tickets with context and outcomes.

375|20|Updated Jan 22, 2026
One-click install
npx skills add https://github.com/dcramer/dex --skill dex
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dex
Source: https://github.com/dcramer/dex/tree/main/plugins/dex/skills/dex
Command: npx skills add https://github.com/dcramer/dex --skill dex

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Dex addresses the challenge of coordinating multi-session work by turning work into structured tickets that preserve full context, decisions, and outcomes for easy handoffs and long-term traceability.

Core Features & Use Cases

  • Ticket-based tasks: Each task, epic, or subtask captures Name, Description, and Result to provide clear context and measurable progress.
  • Persistent context: Context persists across sessions, enabling planning, review, and cross-team collaboration.
  • Hierarchical planning: Supports Epic → Task → Subtask structures for breaking down large initiatives.

Quick Start

Use the dex CLI to create, list, view, and complete tasks. Example: dex create "Plan feature X" --description "Outline scope, dependencies, and acceptance criteria" && dex list && dex show <id> && dex complete <id> --result "Plan confirmed"

Frequently Asked Questions about dex

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I manage persistent tasks across multiple CLI sessions?

Dex coordinates multi-session work by creating persistent tickets that retain full context, decisions, and outcomes, ensuring long-term traceability and easy handoffs across different sessions.

What is the best way to break down large epics into subtasks via command line?

Breaking down large initiatives uses hierarchical Epic, Task, and Subtask tickets, capturing Name, Description, and Result for each item to provide clear context and measurable progress.

How do I create and complete a ticket using the dex CLI?

You create and complete a ticket by running the create command with a name and description, then executing the complete command with the ticket ID and a result argument to record the outcome.

Do I need a Node environment to use the dex CLI for task management?

Yes, you need a Node-based environment to use the dex CLI for task management. The CLI must be installed and operable within this environment to execute its task coordination commands.

How does persistent ticketing handle task blockers and history?

Persistent ticketing handles task blockers and history by applying optional subtasks and blockers to tickets, preserving full context and provenance across long-running workflows for critical review and cross-team collaboration.