stream-chain

Chains sequential prompts into multi-step agent workflows with context passing.

Updated May 8, 2026
One-click install
npx skills add https://github.com/FrekiManagarm/d-chambaud --skill stream-chain-frekimanagarm
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: stream-chain
Source: https://github.com/FrekiManagarm/d-chambaud/tree/main/.agents/skills/stream-chain
Command: npx skills add https://github.com/FrekiManagarm/d-chambaud --skill stream-chain-frekimanagarm

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Coordinating multi-step AI workflows manually requires copying outputs between prompts, losing context and wasting effort. This Skill automates sequential prompt chaining so each step's output flows directly into the next, enabling complex data transformations and multi-agent pipelines without manual handoffs. ## Core Features & Use Cases - Custom Chains: Run arbitrary prompt sequences (minimum 2 steps) where each step receives the full output of the previous one, with configurable timeouts, verbose logging, and debug mode. - Predefined Pipelines: Execute built-in workflows for analysis, refactoring, testing, and optimization, each with structured multi-step logic. - Custom Pipeline Definitions: Define reusable named pipelines in a JSON config file for repeated workflows like security audits or documentation generation. - Use Case: Run a security audit chain that scans for vulnerabilities, categorizes issues by severity, proposes fixes, and generates security test cases in one command. ## Quick Start Ask the agent to run a stream chain that analyzes the codebase structure, identifies improvement areas, and generates an action plan.

Frequently Asked Questions about stream-chain

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

FAQPage Schema
How do I chain multiple AI prompts into a sequential workflow?▼

Use the run command with two or more prompts as arguments. Each prompt becomes a step, and the full output of each step is passed as context to the next, enabling multi-stage processing without manual copying.

What predefined pipelines are available for code workflows?▼

Four built-in pipelines exist: analysis (structure mapping and issue detection), refactor (prioritized code improvements), test (coverage analysis and test generation), and optimize (profiling and performance improvements).

Can I define custom reusable pipelines in a config file?▼

Yes. Add named pipeline definitions with prompt arrays and optional timeouts under streamChain.pipelines in the .Codex-flow/config.json file, then execute them by name with the pipeline command.

Why does a stream chain step time out during execution?▼

Steps default to a 30-second timeout, which is too short for complex analysis or implementation tasks. Increase it with the --timeout flag, using 45-60 seconds for analysis and 60-120 seconds for complex workflows.

How do I debug context not flowing between chain steps?▼

Run the chain with the --debug flag to enable full logging of execution and context passing. This reveals whether previous step outputs are being correctly injected into subsequent prompts.