task-management

Name: task-management
Availability: InStock
Author: mmarcus006

Track features and subtasks with dependencies via a CLI.

1|Updated Jan 28, 2026

Search Tags:#workflow #validation #dependencies #CLI #subtasks #task-management

Ready to run

npx skills add https://github.com/mmarcus006/family-office-ledger --skill task-management-mmarcus006

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: task-management
Source: https://github.com/mmarcus006/family-office-ledger/tree/main/.opencode/skill/task-management
Command: npx skills add https://github.com/mmarcus006/family-office-ledger --skill task-management-mmarcus006

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill provides a CLI-driven system to track, manage, and validate features by breaking them into atomic subtasks with status, dependencies, and clear completion criteria.

Core Features & Use Cases

Task breakdown and tracking: Create and monitor features and their subtasks, with statuses and progress.
Dependency-aware planning: Ensure subtasks only become active when dependencies are satisfied, enabling safe parallel work.
Validation and integrity checks: Validate task.json and subtask.json structures to detect inconsistencies and blockers.

Quick Start

Use this skill to start managing a feature by creating a task.json and subtasks, then query status, next tasks, and completion.

Frequently Asked Questions about task-management

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

FAQPage Schema

How do I track feature subtasks and dependencies in a CLI environment?▼

You can track feature subtasks and dependencies using a CLI-driven system that manages JSON schemas for tasks and subtasks, ensuring accurate status counts and runtime validation. It provides a router-based CLI to monitor progress and query next active items safely.

What is dependency-aware task validation for software projects?▼

Dependency-aware task validation checks task.json and subtask.json structures to detect inconsistencies and blockers. It ensures subtasks only become active when their dependencies are satisfied, enabling safe parallel work and accurate progress visibility for product development teams.

How do I structure JSON files for atomic subtask breakdown?▼

You structure atomic subtask breakdowns by creating task.json and subtask.json files with schemas defining status, dependencies, and completion criteria. The CLI system validates these structures at runtime to maintain integrity and detect blockers across your software project.

Can I use this task-management system for parallel work in product development?▼

Yes, you can use this task-management system for parallel work in product development. It applies dependency-aware planning to ensure subtasks become active only when dependencies are satisfied, allowing teams to work in parallel without encountering blockers or status inconsistencies.

What's the best way to validate task structures and detect blockers?▼

The best way to validate task structures and detect blockers is using a CLI system that performs runtime validation on JSON schemas. It checks task and subtask dependencies to identify inconsistencies, ensuring accurate counts and statuses before subtasks become active.

Why are my subtask statuses not updating correctly during task orchestration?▼

Subtask statuses may not update correctly due to JSON schema inconsistencies or unsatisfied dependencies. The CLI system applies runtime validation to detect these blockers, ensuring subtasks only become active when dependencies are met and maintaining accurate progress counts.