dynamic-workflows

Coordinate multi-phase tasks with a workflow coordinator and daemon-backed subagents.

22|2|Updated Feb 28, 2026
One-click install
npx skills add https://github.com/patleeman/neon-pilot --skill dynamic-workflows
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dynamic-workflows
Source: https://github.com/patleeman/neon-pilot/tree/main/extensions/system-dynamic-workflows/skills/dynamic-workflows
Command: npx skills add https://github.com/patleeman/neon-pilot --skill dynamic-workflows

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Coordinate complex tasks by using a dedicated workflow coordinator instead of a single foreground command.

Core Features & Use Cases

  • Explicit phase-driven coordination for multi-step tasks.
  • Durable transcripts and logs that track progress and results across subagents.
  • Parallel fanout and daemon-backed workflows for scalable automation.
  • Workflow spawning, monitoring, and result aggregation within a single runtime.

Quick Start

Invoke a multi-phase workflow with the workflow tool to coordinate a daemon-backed subagent set and observe progress in transcripts.

Frequently Asked Questions about dynamic-workflows

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

FAQPage Schema
How do I coordinate multi-phase tasks with parallel subagents?

Multi-phase task coordination is handled by using a dedicated workflow coordinator instead of a single foreground command. This approach explicitly drives parallel subagents through complex, multi-step investigations while maintaining a durable runtime transcript.

What is the best way to orchestrate daemon-backed workflows for automation?

Orchestrating daemon-backed workflows involves spawning, monitoring, and aggregating results from a subagent set within a single runtime. A dedicated workflow tool coordinates the fanout and manages scalable automation processes.

How do I track progress and logs across parallel subagent investigations?

Tracking progress across parallel subagents is achieved through durable transcripts and logs. The workflow coordinator automatically records these results to the Workflows page, providing a persistent record of each phase.

Does my runtime environment need specific API support for workflow orchestration?

Workflow orchestration requires a host runtime that exposes a workflow API, supports subagent spawning, and records progress to transcripts. These constraints ensure the coordinator can manage daemon-backed tasks effectively.

When should I use a dedicated workflow coordinator instead of a single foreground command?

A dedicated workflow coordinator should be used instead of a single foreground command when your tasks require explicit phase-driven coordination, parallel fanout, and durable transcripts for complex automation.