workflows

Orchestrate parallel sub-agent runs with automatic result aggregation.

28|14|Updated Mar 2, 2026
One-click install
npx skills add https://github.com/ai-ecoverse/slicc --skill workflows-ai-ecoverse
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: workflows
Source: https://github.com/ai-ecoverse/slicc/tree/main/packages/vfs-root/workspace/skills/workflows
Command: npx skills add https://github.com/ai-ecoverse/slicc --skill workflows-ai-ecoverse

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill eliminates the inefficiency of sequential turn-by-turn processing for large, parallelizable tasks such as codebase-wide sweeps, cross-source research, multi-source data aggregation, and multi-angle planning, which would require excessive manual effort and context switching if handled one step at a time.

Core Features & Use Cases

  • Parallel Sub-Agent Orchestration: Fan out independent sub-tasks to multiple parallel sub-agents for faster execution, with automatic aggregation of results into a single output.
  • Non-Blocking Execution: Run workflows in the background without blocking your current turn, with results delivered automatically when complete — no manual polling or waiting required.
  • Reusable Command Saving: Save successful workflow runs as persistent, reusable commands that can be invoked with custom JSON arguments for repeated use cases.
  • Use Case Example: Run a parallel audit of all packages in a monorepo to collect TODO comments, security issues, or lint errors, then compile the findings into a single consolidated report.

Quick Start

Use the workflows skill to run a parallel audit of all packages in the current codebase to collect all TODO comments and return a consolidated list of findings.

Frequently Asked Questions about workflows

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

FAQPage Schema
How do I run parallel agent workflows for large-scale codebase sweeps?

To run parallel agent workflows for large-scale codebase sweeps, you can fan out independent sub-tasks to multiple parallel sub-agents. This approach automatically aggregates results into a single output, eliminating inefficient sequential turn-by-turn processing.

Can I execute batch processing tasks in the background without blocking my current turn?

Yes, you can execute batch processing tasks in the background without blocking your current turn. Workflows support non-blocking execution where results are delivered automatically upon completion, entirely eliminating the need for manual polling or waiting.

What is the best way to orchestrate multi-angle planning across parallel sub-agents?

The best way to orchestrate multi-angle planning across parallel sub-agents is using a plain-JS orchestration API. This API allows you to define workflow metadata, launch parallel agent runs, and automatically aggregate the independent results into a consolidated output.

How do I save successful workflow runs as reusable commands for repeated task orchestration?

You can save successful workflow runs as persistent, reusable commands for repeated task orchestration by utilizing the skill's built-in saving feature. These saved commands can then be invoked later with custom JSON arguments for repeated use cases.

Does parallel sub-agent orchestration support cross-source research and multi-source data aggregation?

Yes, parallel sub-agent orchestration fully supports cross-source research and multi-source data aggregation. It fans out independent sub-tasks to multiple agents for faster execution and automatically aggregates the findings into a single consolidated report.

What are the limitations of using sequential turn-by-turn processing for parallelizable tasks?

The limitation of using sequential turn-by-turn processing for parallelizable tasks is excessive manual effort and context switching. It is highly inefficient for large tasks like codebase-wide sweeps, making parallel sub-agent orchestration a better approach.