task-system

Manage persistent project tasks with CLI-based YAML state files.

4|Updated Mar 5, 2026
One-click install
npx skills add https://github.com/lirrensi/agent-sommelier --skill task-system-lirrensi
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: task-system
Source: https://github.com/lirrensi/agent-sommelier/tree/main/skills/task-system
Command: npx skills add https://github.com/lirrensi/agent-sommelier --skill task-system-lirrensi

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill solves the problem of losing project context and momentum by organizing agent and human work into a persistent, in-repo task timeline with priorities, statuses, and typed dependencies.

Core Features & Use Cases

  • Persistent, file-based task management: Maintains permanent history in .agents/tasks/ (active tasks in tasks.yaml, archived tasks in closed.yaml) with an editable free-form inbox.md.
  • Priorities, statuses, and ready/blocked queues: Supports 12 task statuses and numeric priorities (p0–p4) and lets you find what is actionable next (tasks ready) versus what is blocked by blocks dependencies (tasks blocked, tasks next --skip-blocks).
  • Typed dependency tracking: Records dependencies in id:type form (blocks, parent, child, discovered, relates) and surfaces dependency graphs and inline resolution in task details.
  • Dependency-aware task discovery: Finds unblocked work and can orient a new session by checking tasks status and tasks ready proactively.

Quick Start

Ask your agent to convert your current inbox into structured tasks, then confirm what it will create and clear the inbox after processing.

Frequently Asked Questions about task-system

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

FAQPage Schema
How do I turn unstructured inbox items into structured tasks with persistent history?

To turn unstructured inbox items into structured tasks, the system parses free-form entries from `inbox.md` and converts them into prioritized tasks with permanent history stored in `.agents/tasks/` YAML files.

How do I find unblocked work and check task dependencies in a project workflow?

To find unblocked work, use `tasks ready` to surface actionable items, and use `tasks blocked` to identify work stalled by typed `blocks` dependencies within the priority-based task queues.

Can I track project task status and priority levels using file-based state?

Yes, file-based state tracking supports 12 task statuses and numeric priorities from p0 to p4, persisting active tasks in `tasks.yaml` and archived tasks in `closed.yaml` for permanent history.

What is the best way to manage typed dependency graphs for project tasks?

Managing typed dependency graphs involves recording relationships in `id:type` form such as `blocks`, `parent`, or `child`, enabling dependency-aware task discovery and inline resolution in task details.

Does task status tracking work without external databases or server dependencies?

Yes, task status tracking works without external databases by maintaining file-based state exclusively through CLI-only YAML mutations in the `.agents/tasks/` directory using stable `TSK-NNNN` identifiers.

Why are some tasks blocked when querying the next actionable work?

Tasks are blocked when unresolved `blocks` dependencies exist, preventing them from appearing in `tasks ready` queues; you can bypass this orientation by running `tasks next --skip-blocks`.