output-workflow-stop

Stop running Output SDK workflows by ID via the npx command.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Stop a running Output SDK workflow execution. This action terminates the workflow to reclaim resources and prevent further steps from executing.

Core Features & Use Cases

  • Stop a RUNNING workflow via the command: npx output workflow stop <workflowId>.
  • Includes safety considerations and status checks to minimize risk and ensure clean termination.
  • Applicable across development, staging, and production environments when workflows become unresponsive or undesired.

Quick Start

Use the stop command to terminate a workflow by its ID.

Frequently Asked Questions about output-workflow-stop

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

FAQPage Schema
How do I stop a running Output SDK workflow that is stuck?

To stop a stuck Output SDK workflow, run the command `npx output workflow stop <workflowId>`. This terminates the workflow execution, halts further steps, and frees up the allocated resources safely.

What is the safest way to terminate a long-running workflow in production?

The safest way to terminate a long-running production workflow is using the `npx output workflow stop` command, which includes safety checks and status verification to ensure clean termination and proper post-stop state handling.

Can I cancel an unresponsive workflow in staging or development environments?

Yes, you can cancel unresponsive workflows across development, staging, and production environments. The stop command applies safety considerations to minimize risk and ensure clean termination regardless of the environment.

Does the output workflow stop command verify status before terminating?

Yes, the output workflow stop command verifies the workflow status before terminating execution. It enforces termination with safety checks and handles the post-stop state to prevent resource leaks.

Why do I need to stop a misconfigured workflow instead of letting it finish?

Stopping a misconfigured workflow prevents undesired steps from executing and immediately reclaims system resources. Terminating the workflow minimizes potential risks and ensures clean state handling across your environments.