stream-chain

Featured

Stream-JSON chaining for multi-agent pipelines, data transformation, and sequential workflows

AI & Automation 338 stars 27 forks Updated 3 weeks ago Apache-2.0

Install

View on GitHub

Quality Score: 94/100

Stars 20%
84
Recency 20%
90
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

# Stream-Chain Skill Execute sophisticated multi-step workflows where each agent's output flows into the next, enabling complex data transformations and sequential processing pipelines. ## Overview Stream-Chain provides two powerful modes for orchestrating multi-agent workflows: 1. **Custom Chains** (`run`): Execute custom prompt sequences with full control 2. **Predefined Pipelines** (`pipeline`): Use battle-tested workflows for common tasks Each step in a chain receives the complete output from the previous step, enabling sophisticated multi-agent coordination through streaming data flow. --- ## Quick Start ### Run a Custom Chain ```bash claude-flow stream-chain run \ "Analyze codebase structure" \ "Identify improvement areas" \ "Generate action plan" ``` ### Execute a Pipeline ```bash claude-flow stream-chain pipeline analysis ``` --- ## Custom Chains (`run`) Execute custom stream chains with your own prompts for maximum flexibility. ### Syntax ```bash claude-flow stream-chain run <prompt1> <prompt2> [...] [options] ``` **Requirements:** - Minimum 2 prompts required - Each prompt becomes a step in the chain - Output flows sequentially through all steps ### Options | Option | Description | Default | |--------|-------------|---------| | `--verbose` | Show detailed execution information | `false` | | `--timeout <seconds>` | Timeout per step | `30` | | `--debug` | Enable debug mode with full logging | `false` | ### How Context Flows Each step receive...

Details

Author
spencermarx
Repository
spencermarx/open-code-review
Created
6 months ago
Last Updated
3 weeks ago
Language
TypeScript
License
Apache-2.0

Similar Skills

Semantically similar based on skill content — not just same category

AI & Automation Listed

stream-chain

Stream-JSON chaining for multi-agent pipelines, data transformation, and sequential workflows

0 Updated 1 months ago
SaharBarak
AI & Automation Listed

precision-prompt-chaining

Multi-step prompt chaining skill where each step's output becomes the next step's input, with explicit rules, constraints, and reference tokens between steps. Activates when the user needs to build a complex pipeline of dependent Claude calls — research → outline → draft → edit → publish — where downstream steps must be constrained by upstream outputs without hallucination or drift. Designs chains with named output variables, explicit pass rules, validation gates between steps, and failure recovery conditions. Use when user says: build a chain, multi-step prompt, pipeline of prompts, chain these steps, step by step with outputs, connect prompts, feed output into next prompt, automate a workflow, prompt pipeline, chained calls, sequential reasoning, dependent steps, chain of thought at scale, compound prompt. Do NOT activate for: single-turn questions, simple back-and-forth conversation, cases where one prompt is sufficient for the task. First response: "Prompt Chain Builder active. Describe the full workflow

3 Updated 2 weeks ago
Sandeeprdy1729
AI & Automation Listed

chain

Execute a YAML-defined chain of skill invocations as a single reproducible, audited workflow — with template-driven input piping, schema validation, retry-on-malformed, conditional steps, gates (filesystem / semantic / tool), per-step worktree isolation, and JSONL audit logging. Use when the user says "run the X chain," "execute the X chain on Y," "chain these skills," "run this skill sequence," "run chain," "execute validate-<topic>," or names a chain defined in the workspace `chains/` or `drafts/sample-chains/` directories. Also offer this proactively when the active primary is about to manually run several skills in sequence on the same artifact, where the same sequence is likely to repeat — turning the ad-hoc flow into a chain YAML up-front buys reproducibility, audit trail, and consistent gate enforcement across runs.

0 Updated today
sumitake