task-management

Track and validate feature subtasks with dependency resolution via a CLI.

Updated Sep 13, 2023
One-click install
npx skills add https://github.com/dlwlrmax/.dotfiles --skill task-management-dlwlrmax
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: task-management
Source: https://github.com/dlwlrmax/.dotfiles/tree/main/opencode/.config/opencode/skills/task-management
Command: npx skills add https://github.com/dlwlrmax/.dotfiles --skill task-management-dlwlrmax

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires ts-node, and includes scripts (resource) components.

What problem does it solve? Managing multi-step feature implementations across subagents is error-prone: tasks get lost, dependencies are unclear, and progress is hard to measure. This Skill provides a CLI that reads task JSON files created by the TaskManager subagent and gives you status, readiness, blocking, and validation views. ## Core Features & Use Cases - Progress Tracking: Run status to see per-feature completion percentages and counts of pending, in-progress, completed, and blocked subtasks. - Dependency-Aware Scheduling: Use next, parallel, deps, and blocked to find which subtasks are ready to run, which can run in parallel, and what is blocking others. - Integrity Validation: The validate command checks required fields, sequence uniqueness, dependency references, and circular dependency detection across all task JSON files. - Use Case: After TaskManager breaks a feature into subtasks in .tmp/tasks/, delegate subtasks to coding agents, mark each complete with a summary, and monitor overall progress until the feature's exit criteria are met. ## Quick Start Ask the assistant to show the next eligible tasks for your feature by running the task-management router's next command from the project root.

Frequently Asked Questions about task-management

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

FAQPage Schema
How do I track subtask progress for a feature implementation?▼

Run the router's status command with an optional feature name to see completion percentage and counts of pending, in-progress, completed, and blocked subtasks. Task data is read from JSON files in .tmp/tasks/ at the project root.

How do I find which tasks are ready to run next?▼

Use the next command to list pending subtasks whose dependencies are all completed. The parallel command further filters these to subtasks marked parallel: true that can run concurrently.

What does the validate command check in task files?▼

Validation checks required fields in task.json and subtask files, sequence format and uniqueness, valid status values, dependency references to existing subtasks, self-dependencies, and circular dependency chains. It exits with a non-zero code if any errors are found.

How do I mark a subtask as complete?▼

Run the complete command with the feature slug, sequence number, and a summary of up to 200 characters. The CLI updates the subtask's status and timestamp, then recalculates the completed count in task.json.

Why does the CLI report a dependency not satisfied error?▼

A subtask is only ready when every sequence in its depends_on array is completed. Use the deps command to print the dependency tree and see which prerequisite subtasks are still pending or in progress.