task-management

Track feature subtasks and dependencies by running CLI commands like status, next, and complete. The system stores data in task.json and subtask_xx.json files under .tmp/tasks, showing readiness, blockers, and completion progress for each feature.

Identify blocked tasks and next eligible work using the next command in the CLI. It evaluates dependency trees and subtask statuses to show which features are ready to proceed and which are blocked by incomplete dependencies.

Validate task data integrity by running the validate command. It checks the task.json and subtask_xx.json files under .tmp/tasks to ensure dependency trees are correct and feature data is structurally sound.

You can use this CLI for breaking down large features into smaller subtasks. It applies to CLI-based project workflows where teams decompose features into subtasks and track statuses, dependencies, and completion progress with a completed subtasks archive.

No external dependencies are required to run this project-tracking CLI. It operates independently using scripts to manage task.json and subtask_xx.json files stored locally under the .tmp/tasks directory per feature.

Feature status may not update if the dependency tree is incomplete or task data integrity is broken. Run the validate command to check task.json and subtask_xx.json files for structural errors before using the complete command.