yatl-tasks

Load YAML-frontmatted yatl task data across sessions with dependency graphs.

4|Updated Nov 27, 2025
One-click install
npx skills add https://github.com/brianm/yatl --skill yatl-tasks
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: yatl-tasks
Source: https://github.com/brianm/yatl/tree/main/claude/yatl
Command: npx skills add https://github.com/brianm/yatl --skill yatl-tasks

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

yatl-tasks provides persistent, structured memory for multi-session work, enabling dependencies and context to survive compaction.

Core Features & Use Cases

  • Persist task state across sessions using a YAML-frontmatted Markdown file per task, organized by status directories (open, in-progress, blocked, closed, cancelled).
  • Manage complex dependencies with automatic blocking/unblocking and dependency graphs.
  • Integrate with TodoWrite for rapid execution while preserving long-term context for post-session analysis and audits.

Quick Start

Install yatl, run yatl init in your project, then create and manage multi-session tasks with yatl new, start, log, and close.

Frequently Asked Questions about yatl-tasks

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

FAQPage Schema
How do I preserve task context across multiple sessions after context compaction?

Persistent task memory survives compaction by storing task state in YAML-formatted Markdown files organized by status directories, preserving dependencies and context for resumed work. Each task retains its full history and dependency graph across sessions.

How do I manage task dependencies that automatically block or unblock other tasks?

Automatic dependency management tracks task relationships and blocks downstream tasks when upstream dependencies remain open. Tasks automatically unblock when their dependencies reach closed or cancelled status, maintaining a live dependency graph across the workflow.

What's the best way to structure long-running work that needs to survive context loss?

Long-running work requires structured task files using YAML frontmatter for metadata and status directories for organization. This format ensures context survives compaction by persisting task state, logs, and dependency relationships externally rather than relying on session memory.

Can I use TodoWrite for rapid task execution while keeping long-term persistent memory?

TodoWrite integrates with persistent task management for rapid execution while preserving long-term context. Short-term execution stays in TodoWrite, while task state, dependencies, and session logs persist in structured Markdown files for post-session analysis and audits.

How do I initialize a project for persistent multi-session task management?

Run the initialization command in your project root to set up the task directory structure with status folders for open, in-progress, blocked, closed, and cancelled tasks. Then create tasks using the new task command with YAML frontmatter formatting.

When do I need persistent task memory for workflow management?

Persistent task memory is needed when work spans multiple sessions, involves complex dependencies, or requires context to survive compaction. Scenarios with long-running tasks, blocking relationships, and audit trails benefit from structured state persistence across sessions.