task-management

You can track feature subtasks and dependencies across multiple sprints using a CLI workflow with JSON schemas. It manages status transitions, dependency graphs, and acceptance criteria to enforce repeatable progress.

Run the CLI router script with the 'next' command to find the next eligible task. It evaluates task and subtask dependencies to identify which items are unblocked and ready for work.

Yes, you can validate task and subtask definitions to prevent drift by running the CLI router script with the 'validate' command. It performs integrity checks on your JSON schemas to ensure consistency.

The best way to manage feature work status using a CLI workflow is through a TaskManager integration that tracks progress, identifies blocked tasks, and marks subtasks complete with summaries for audit trails.

Yes, this task-management approach works for software teams coordinating dependencies. It applies to teams managing features with dependency graphs, status updates, and acceptance criteria across multiple sprints.

Your subtasks are blocked by incomplete dependencies, and you can identify their blockers by running the CLI router script with the 'status' command to inspect the dependency graph and task integrity.