tasks

Manage spec.md and tasks.yaml task sets with status tracking and dependency queries.

1|Updated May 4, 2026
One-click install
npx skills add https://github.com/wesbragagt/nixos-config --skill tasks-wesbragagt
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: tasks
Source: https://github.com/wesbragagt/nixos-config/tree/main/home/skills/tasks
Command: npx skills add https://github.com/wesbragagt/nixos-config --skill tasks-wesbragagt

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires pyyaml.

What problem does it solve? It removes the manual overhead of creating and maintaining structured task breakdowns for features, keeping spec documents and task statuses consistent and queryable from the command line. ## Core Features & Use Cases - Spec and Task Set Creation: Delegates to the to-spec skill to generate spec.md, tasks.yaml, and per-task detail packets under .specs/<feature-name>/ when none exist. - Task Status Management: Lists, inspects, and updates task statuses (open, progress, done) via the tasks.py CLI with atomic file writes. - Dependency Awareness: Shows which tasks are ready to start based on completed dependencies and verifies full completion with an exit code. - Use Case: Given a feature description like "Build user authentication system", the skill creates .specs/build-user-auth-system/ with a spec and task breakdown, then tracks each task to completion. ## Quick Start Ask the assistant to create and track a task breakdown for a new feature description or an existing spec directory using the tasks skill.

Frequently Asked Questions about tasks

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

FAQPage Schema
How do I create a task breakdown from a feature description?

Provide the feature description to the tasks skill, which delegates to the to-spec skill to generate spec.md, tasks.yaml, and task detail packets under .specs/<feature-name>/. The feature name is auto-derived from the first four words unless overridden with --name.

How do I update task status in a tasks.yaml file?

Run tasks.py with the set subcommand: uv run tasks.py <path>/tasks.yaml set <key> progress or done. Valid statuses are open, progress, and done, and the file is updated atomically via a temporary file replace.

How do I find which tasks are ready to start?

Use the ready subcommand: uv run tasks.py <path>/tasks.yaml ready. It lists open tasks whose dependencies are all marked done, so you always know the next actionable work item.

Can the tasks skill work with an existing prd.md file?

Yes. If the given path contains only a legacy prd.md, the skill treats it as input context for the to-spec skill, which produces spec.md and tasks.yaml alongside it before tracking begins.

What happens when tasks.yaml verify finds incomplete tasks?

The verify subcommand exits with code 1 and prints each incomplete task with its status to stderr. When all tasks are done it prints a confirmation and exits with code 0, making it suitable for CI checks.