output-workflow-start

Start Output SDK workflows asynchronously and return a workflow ID immediately.

430|12|Updated Mar 13, 2026
One-click install
npx skills add https://github.com/growthxai/output --skill output-workflow-start
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: output-workflow-start
Source: https://github.com/growthxai/output/tree/main/coding_assistants/claude/plugins/outputai/skills/output-workflow-start
Command: npx skills add https://github.com/growthxai/output --skill output-workflow-start

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Initiates Output SDK workflows asynchronously so you receive a workflow ID immediately while the actual work runs in the background.

Core Features & Use Cases

  • Asynchronous start: Launch workflows without blocking your terminal.
  • Parallel execution: Kick off multiple workflows and monitor them independently.
  • Status & results workflow: Retrieve status and results later using the provided IDs.

Quick Start

Invoke the start command to launch a workflow asynchronously with a specified name and optional input.

Frequently Asked Questions about output-workflow-start

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

FAQPage Schema
How do I start an asynchronous workflow without blocking my CLI?

You can start an asynchronous workflow by invoking the start command with a specified name and optional input, which returns a workflow ID immediately while the workflow runs in the background.

Can I execute multiple workflows in parallel and monitor them independently?

Yes, you can kick off multiple workflows in parallel and monitor them independently using the unique workflow ID returned for each asynchronous start to retrieve status and results.

How do I retrieve the status and results of a background workflow?

You retrieve workflow status and results by using the workflow ID provided during the asynchronous start to check execution progress and fetch final outputs later.

What input methods are supported when launching an async workflow?

Supported input methods for launching an async workflow include inline JSON passed directly in the command syntax or file-based inputs for providing workflow data.

When should I use asynchronous workflow execution instead of synchronous?

Use asynchronous workflow execution for long-running workflows, batch starts, and parallel execution scenarios where non-blocking monitoring is required to avoid terminal blocking.