orchestrator

Coordinate Task Decomposition Protocol workflows from specification to execution.

19|1|Updated Nov 25, 2025
One-click install
npx skills add https://github.com/Dowwie/tasker --skill orchestrator-dowwie
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: orchestrator
Source: https://github.com/Dowwie/tasker/tree/main/internal/skills/_archived/orchestrator
Command: npx skills add https://github.com/Dowwie/tasker --skill orchestrator-dowwie

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

Thin orchestrator for Task Decomposition Protocol v2. Supports two modes: Plan Mode (/plan) to decompose a spec into a task DAG, and Execute Mode (/execute) to run tasks via isolated subagents. Delegates all state management to the tasker CLI, coordinating the lifecycle from specification to implementation.

Core Features & Use Cases

  • Thin coordination layer that orchestrates the three-stage workflow: specify → plan → execute
  • Dispatches sub-agents for planning, physical mapping, and task execution with consistent context
  • Ensures commits and logging are enforced through hooks to provide traceability across the workflow
  • Provides entry points and guidance for handling specs, artifacts, and FSM artifacts to support end-to-end planning

Quick Start

Start with /specify to develop the spec, then run /plan to decompose into tasks and /execute to implement and verify

Frequently Asked Questions about orchestrator

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

FAQPage Schema
How do I automate task decomposition from specification to execution in Claude Code?▼

Task decomposition is automated by a thin orchestrator that coordinates the specify, plan, and execute stages. It dispatches isolated subagents for planning and execution while delegating state management to the tasker CLI.

How does plan-to-execute workflow coordination handle phase transitions and artifacts?▼

Plan-to-execute coordination uses a lightweight FSM to manage phase transitions and artifact management. It enforces commits and logging through hooks to provide traceability across the specification, planning, and execution lifecycle.

Can I use tasker CLI for stateful task management within a plan and execute workflow?▼

Yes, the tasker CLI handles all state management for stateful tasks within the workflow. The orchestrator acts as a thin coordination layer, delegating state tracking and FSM integration entirely to the CLI.

What is the best way to decompose a spec into a task DAG for isolated subagent execution?▼

Decomposing a spec into a task DAG is handled by Plan Mode, which breaks down specifications into executable tasks. Execute Mode then runs these tasks via isolated subagents with consistent context.

Do I need frontmatter metadata and FSM artifacts to coordinate task decomposition workflows?▼

Yes, frontmatter metadata and FSM artifacts are required for end-to-end planning and stateful task coordination. The orchestrator satisfies these requirements to support phase-driven spawning and artifact verification.

Why does the orchestrator enforce commits and logging through hooks during task execution?▼

Commits and logging are enforced through hooks to provide traceability across the plan-to-execute workflow. This ensures that artifact management and phase transitions remain auditable throughout the task lifecycle.