workflow-conductor

Route issues or task bundles to the next ADL skill while enforcing policy and recording routing evidence.

4|1|Updated Feb 3, 2026
One-click install
npx skills add https://github.com/danielbaustin/agent-design-language --skill workflow-conductor
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: workflow-conductor
Source: https://github.com/danielbaustin/agent-design-language/tree/main/adl/tools/skills/workflow-conductor
Command: npx skills add https://github.com/danielbaustin/agent-design-language --skill workflow-conductor

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

Lightweight orchestrator over the ADL operational skills. Its job is to inspect the current workflow state, choose the next appropriate lifecycle or editor skill, route work to the matching editor skill, apply explicit skill/subagent execution policy, record workflow-compliance outcomes, preserve bound issue worktree identity as first-class routing evidence, emit a bounded routing artifact, and when explicitly enabled dispatch one bounded downstream skill subtask and stop at that boundary.

Core Features & Use Cases

  • Inspect current workflow state and choose the next appropriate ADL skill
  • Route card-local work to the matching editor skill or lifecycle skill
  • Enforce policy and record workflow-compliance outcomes
  • Emit bounded routing artifacts and optionally dispatch one downstream subtask
  • Preserve issue/worktree identity across routing for auditing and traceability

Quick Start

Inspect the current workflow state, route to the next appropriate ADL skill, and record the routing artifact.

Frequently Asked Questions about workflow-conductor

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

FAQPage Schema
How do I route issues to the next workflow skill while enforcing execution policy?

Issue routing validates the target and policy block, enforces compliance, and emits a bounded artifact directing the next ADL skill. It optionally dispatches one downstream subtask and preserves worktree identity for auditing.

What is a routing artifact in workflow orchestration and when do I need one?

A routing artifact is a bounded audit record generated when routing tasks to the next lifecycle or editor skill. You need it to preserve issue worktree identity and provide evidence of policy enforcement during workflow compliance checks.

How do I apply policy checks before dispatching a downstream task bundle?

Policy enforcement occurs before dispatching a downstream task bundle by validating the policy block input. The orchestrator applies the specified skill execution policy, records the compliance outcome, dispatches one bounded subtask, and stops at that boundary.

Does workflow orchestration support routing for worktrees and pull requests?

Yes, workflow orchestration supports single-target routing decisions including route worktree, route issue, route branch, route pull request, and route task bundle. It validates the concrete target and returns a bounded artifact for each type.

What are the limitations of using a lightweight orchestrator for task routing?

This lightweight orchestrator limits downstream dispatch to one bounded subtask and then stops at that boundary. It is designed for single-target routing decisions only, requiring explicit policy block validation rather than handling complex multi-step branching.

Can I use workflow orchestration without a concrete repo root and policy block?

No, workflow orchestration requires both a valid repo root and a concrete target to validate inputs before routing. The policy block is also mandatory for enforcing execution rules and generating the compliance audit artifact.