dex

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.

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.

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.

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.

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.

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.