dex

Create persistent tasks with subtasks, blockers, and verification criteria.

9|Updated Dec 30, 2025

Search Tags:#workflow #cli #verification #task-management #project-management #dex

Ready to run

npx skills add https://github.com/eliaskc/kajji --skill dex-eliaskc

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: dex
Source: https://github.com/eliaskc/kajji/tree/main/.agents/skills/dex
Command: npx skills add https://github.com/eliaskc/kajji --skill dex-eliaskc

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Dex enables teams to convert chaotic, ad-hoc work into persistent, context-rich tickets that survive across sessions.

Core Features & Use Cases

Create, describe, and update tasks with names, descriptions, and results
Support for subtasks, blockers, and verification trails for auditability
Use cases: planning, handoffs, and long-running initiatives

Quick Start

Create a new dex task with a concise name and a detailed description to start tracking work.

Frequently Asked Questions about dex

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

FAQPage Schema

How do I create persistent tasks for multi-session project management workflows?▼

You create persistent tasks for multi-session workflows by defining a concise name, detailed description, and verification criteria. This approach converts ad-hoc work into context-rich tickets that remain auditable across sessions and team handoffs.

What is the best way to track complex work with subtasks and blockers across different sessions?▼

Tracking complex work across sessions involves organizing tasks into persistent structures with subtasks and blockers. This method ensures enduring context and auditability for long-running initiatives, preventing details from being lost between project handoffs.

Can I use YAML frontmatter to manage task verification criteria and audit trails?▼

Yes, you can use YAML frontmatter in a SKILL.md file to manage task verification criteria. This allows you to maintain auditable task descriptions, track blockers, and ensure verification trails survive across multiple team sessions.

How do I document project handoffs so the context survives across different teams?▼

You document project handoffs by creating persistent, context-rich tickets that capture task names, descriptions, and results. This ensures the workflow context survives across different teams and sessions without losing verification trails.

Do I need any specific dependencies to organize ad-hoc work into auditable tasks?▼

No specific dependencies are required to organize ad-hoc work into auditable tasks. The skill operates independently, using YAML frontmatter and optional scripts to convert chaotic workflows into persistent, context-rich tickets.

When should I use persistent task management for complex project workflows?▼

You should use persistent task management for complex workflows when handling multi-session projects, team handoffs, or long-running initiatives. It is essential when work requires enduring context, subtask tracking, and strict verification criteria for auditability.