What is the primary role of the Tasker Orchestrator?

It acts as a thin coordination layer that guides Claude through the process of planning tasks from a spec and executing those tasks via sub-agents.

Does this skill require a specification file?

Yes, /plan requires a markdown spec (usually generated via /specify) to decompose requirements into a task DAG.

Why is absolute path management important for this skill?

Sub-agents run in isolated contexts; using absolute paths ensures they can correctly resolve the .tasker directory regardless of their specific environment.

How does it handle existing projects?

It performs an automated analysis of the target directory to identify tech stacks, project structures, and coding patterns before starting the planning phase.

Tasker Orchestrator

Name: Tasker Orchestrator
Author: Dowwie

byDowwie

•

Productivity & Workflow

Coordinates agentic development workflows through spec-driven planning and sub-agent execution.

About

The Tasker Orchestrator is a specialized coordination layer for the Task Decomposition Protocol v2, designed to manage complex software development tasks within Claude Code. It functions by breaking down high-level specifications into structured task Directed Acyclic Graphs (DAGs) using the /plan mode, and subsequently implementing those tasks through isolated sub-agents in /execute mode. By centralizing directory initialization, mandatory runtime logging, and absolute path management, it provides a reliable framework for autonomous development while delegating state management to the tasker CLI.

Key Features

Mandatory activity logging for sub-agent transparency
8 GitHub stars
Dual-mode operation for logical planning and physical execution
Seamless integration with /specify for requirement gathering
Project analysis for both greenfield and existing codebases
Automated .tasker directory initialization and structure management

Use Cases

Managing autonomous sub-agents to implement multi-file code changes
Decomposing complex feature requests into actionable development plans
Maintaining persistent task state across long-running development sessions

About

Key Features

Mandatory activity logging for sub-agent transparency
8 GitHub stars
Dual-mode operation for logical planning and physical execution
Seamless integration with /specify for requirement gathering
Project analysis for both greenfield and existing codebases
Automated .tasker directory initialization and structure management

Use Cases

Managing autonomous sub-agents to implement multi-file code changes
Decomposing complex feature requests into actionable development plans
Maintaining persistent task state across long-running development sessions