dex

Coordinate persistent ticket-based tasks with verified outcomes across sessions.

41|4|Updated May 6, 2026

Search Tags:#task management #workflow automation #git workflow #verification evidence #issue synchronization #multi-session coordination

Ready to run

npx skills add https://github.com/markerikson/opencode-config-example --skill dex-markerikson

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: dex
Source: https://github.com/markerikson/opencode-config-example/tree/main/config/skill/dex
Command: npx skills add https://github.com/markerikson/opencode-config-example --skill dex-markerikson

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Dex helps you break down complex, multi-session work into well-scoped, persistent tickets so decisions, context, and verification are captured for future you and handoffs.

Core Features & Use Cases

Ticket-based task structure: Store a one-line ticket name plus a rich description and a complete result to make work understandable on its own.
Persistent, multi-session coordination: Maintain context across sessions using files in .dex instead of ephemeral in-chat task tools.
Verification and completion guardrails: Encourage completing tasks only after implementation and verification, with evidence (tests, builds, manual testing) and clear acceptance criteria.

Quick Start

Use the dex skill to create a new ticket for a feature you plan to implement across multiple sessions, then start and complete it with verified results.

Frequently Asked Questions about dex

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

FAQPage Schema

How do I track complex software work across multiple sessions?▼

To track complex software work across multiple sessions, you need persistent ticket-based task coordination. This approach stores context and decisions in files, ensuring work is understandable for future sessions and handoffs rather than relying on ephemeral in-chat tracking.

What is the best way to manage multi-session implementation and decision recording?▼

The best way to manage multi-session implementation and decision recording is using persistent tickets with rich descriptions. By capturing context and verification outcomes in files, you create a durable record that survives across sessions and supports clear handoffs.

How do I ensure tasks are only completed after implementation and verification?▼

To ensure tasks are completed only after implementation and verification, use completion guardrails that require strict result evidence. You must provide verification evidence like tests, builds, or manual testing results alongside clear acceptance criteria before closing a ticket.

Can I synchronize issues and stories using git workflow commits?▼

Yes, you can synchronize issues and stories using git workflow commits. By applying safe linkage rules, you coordinate ticket-based tasks with your repository, ensuring that issue synchronization is tied directly to verified commit evidence.

When should I use persistent ticket-based task management over ephemeral tracking?▼

You should use persistent ticket-based task management over ephemeral tracking when handling complex, multi-session software work. If your scenario involves decision recording, handoffs, and strict result verification, ephemeral tracking is insufficient and persistent files are required.