stream-chain
Skill4 starsChanged 27 days agoMITView on GitHub
Stream-JSON chaining for multi-agent pipelines, data transformation, and sequential workflows
34 other projects use a version of this, 13 of them edited.
Adopted by
Most recently taken up by
- poizoncoded/skillsedited, first seen Nov 1, 2026
- OpenxIntelligence/Coding-Agent-Skillsword for word, first seen Nov 1, 2026
- proffesor-for-testing/agentic-qeedited, first seen Oct 25, 2026
- ruvnet/rufloedited, first seen Oct 21, 2026
- alexandremaciel-ai/openclaw-dashboard-v2word for word, first seen Oct 15, 2026
- Arzeroe/Claude-skillsedited, first seen Oct 13, 2026
Used with
Projects with it also use V3 DDD Architecture, V3 Memory Unification and 10 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
ruvnetSkillV3 DDD Architecture
Domain-Driven Design architecture for claude-flow v3. Implements modular, bounded context architecture with clean separation of concerns and microkernel pattern.
Also in 27 projects that use this
ruvnetSkillV3 Memory Unification
Unify 6+ memory systems into AgentDB with HNSW indexing for 150x-12,500x search improvements. Implements ADR-006 (Unified Memory Service) and ADR-009 (Hybrid Memory Backend).
Also in 27 projects that use this
nbossnSkillworker-benchmarks
Run comprehensive worker system benchmarks and performance analysis
Also in 9 projects that use this
ZekiogSkillagent-agent
Agent skill for agent - invoke with $agent-agent
Also in 5 projects that use this
ZekiogSkillagent-analyze-code-quality
Agent skill for analyze-code-quality - invoke with $agent-analyze-code-quality
Also in 5 projects that use this
- +3 more from ruvnet
- +4 more from Zekiog
Other versions34 projects use a version of this.
Word for word · 21
- ruvnet/wifi-densepose★ 103k100% same
- ruvnet/RuView★ 103k100% same
- ruvnet/ruvector★ 4.7k100% same
- ruvnet/RuVector★ 4.7k100% same
- ruvnet/agentic-flow★ 838100% same
- ruvnet/ruv-FANN★ 388100% same
- spencermarx/open-code-review★ 382100% same
- chatman-media/timeline-studio★ 224100% same
- ruvnet/midstream★ 151100% same
- tokendad/NesVentory★ 93100% same
11 more not listed
Edited · 13
- ruvnet/claude-flow★ 80k100% same
- ruvnet/ruflo★ 79k100% same
- proffesor-for-testing/agentic-qe★ 524100% same
- ayushcodes10/echo-mem★ 290% same
- echo-mem/echo-mem★ 290% same
- poizoncoded/skills★ 2100% same
- Zekiog/ruflo★ 2100% same
- fidgetcoding/fidgetflo★ 189% same
- jpoindexter/theft-kit★ 1100% same
- Soulcynics404/AgentForge★ 1100% same
3 more not listed
Wrote their own version · 0
None found.
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository169 other files it gives its agents.
- epub-skill/CLAUDE.mdCLAUDE.md
- linear-cli-skill/CLAUDE.mdCLAUDE.md
- AgentDB Advanced FeaturesSkill
- AgentDB Learning PluginsSkill
- AgentDB Memory PatternsSkill
- AgentDB Performance OptimizationSkill
- AgentDB Vector SearchSkill
- agent-evalSkill
- agentic-jujutsuSkill
- agile-product-ownerSkill
- ai-tool-pickerSkill
- algorithmic-artSkill
- api-connectorSkill
- api-design-patternsSkill
- architecture-diagram-creatorSkill
- article-extractorSkill
- aws-agentic-aiSkill
- aws-cdk-developmentSkill
- aws-cost-operationsSkill
- aws-serverless-edaSkill
- biogeobearsSkill
- brainstormingSkill
- brand-guidelinesSkill
- canvas-designSkill
- capa-officerSkill
- ceo-advisorSkill
- changelog-generatorSkill
- code-auditorSkill
- codebase-documenterSkill
- code-executionSkill
- code-explainerSkill
- code-refactorSkill
- code-reviewerSkill
- code-transferSkill
- content-creatorSkill
- content-research-writerSkill
- conversation-analyzerSkill
- csv-data-summarizerSkill
- cto-advisorSkill
- d3-vizSkill
- dashboard-creatorSkill
- defense-in-depthSkill
- deploy-itSkill
- developer-growth-analysisSkill
- dispatching-parallel-agentsSkill
- doc-coauthoringSkill
- docxSkill
- domain-name-brainstormerSkill
- dwa-councilSkill
- error-fixerSkill
- escalation-reasoningSkill
- evaluator-optimizerSkill
- executing-plansSkill
- extract-from-pdfsSkill
- fda-consultant-specialistSkill
- feature-planningSkill
- file-operationsSkill
- file-organizerSkill
- finishing-a-development-branchSkill
- firebase-buddySkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
7 rules. 5 are common, 0 are distinctive, and 2 are very specific to this project.
5
Common
Most of the 13 edited versions we read keep these.
0
Distinctive
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Common: line 174
Prioritization: Create ranked refactoring plan
- Common: line 193
Test Design: Create test cases for critical functions
- Common: line 409
Use chains for iterative improvement:
- Common: line 467
If steps timeout, increase timeout value:
- Very specific: line 475
If context not flowing properly, use --debug:
- Common: line 483
Verify pipeline name and custom definitions:
- Very specific: line 563
Use run for custom workflows and pipeline for battle-tested solutions.
“Common” is measured: kept by at least 6 in 10 of the 13 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
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:
- Custom Chains (
run): Execute custom prompt sequences with full control - 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
claude-flow stream-chain run \
"Analyze codebase structure" \
"Identify improvement areas" \
"Generate action plan"Execute a Pipeline
claude-flow stream-chain pipeline analysisCustom Chains (run)
Execute custom stream chains with your own prompts for maximum flexibility.
Syntax
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 receives the previous output as context:
Step 1: "Write a sorting function"
Output: [function implementation]
Step 2 receives:
"Previous step output:
[function implementation]
Next task: Add comprehensive tests"
Step 3 receives:
"Previous steps output:
[function + tests]
Next task: Optimize performance"Examples
Basic Development Chain
claude-flow stream-chain run \
"Write a user authentication function" \
"Add input validation and error handling" \
"Create unit tests with edge cases"Security Audit Workflow
claude-flow stream-chain run \
"Analyze authentication system for vulnerabilities" \
"Identify and categorize security issues by severity" \
"Propose fixes with implementation priority" \
"Generate security test cases" \
--timeout 45 \
--verboseCode Refactoring Chain
claude-flow stream-chain run \
"Identify code smells in src/ directory" \
"Create refactoring plan with specific changes" \
"Apply refactoring to top 3 priority items" \
"Verify refactored code maintains behavior" \
--debugData Processing Pipeline
claude-flow stream-chain run \
"Extract data from API responses" \
"Transform data into normalized format" \
"Validate data against schema" \
"Generate data quality report"Predefined Pipelines (pipeline)
Execute battle-tested workflows optimized for common development tasks.
Syntax
claude-flow stream-chain pipeline <type> [options]Available Pipelines
1. Analysis Pipeline
Comprehensive codebase analysis and improvement identification.
claude-flow stream-chain pipeline analysisWorkflow Steps:
- Structure Analysis: Map directory structure and identify components
- Issue Detection: Find potential improvements and problems
- Recommendations: Generate actionable improvement report
Use Cases:
- New codebase onboarding
- Technical debt assessment
- Architecture review
- Code quality audits
2. Refactor Pipeline
Systematic code refactoring with prioritization.
claude-flow stream-chain pipeline refactorWorkflow Steps:
- Candidate Identification: Find code needing refactoring
- Prioritization: Create ranked refactoring plan
- Implementation: Provide refactored code for top priorities
Use Cases:
- Technical debt reduction
- Code quality improvement
- Legacy code modernization
- Design pattern implementation
3. Test Pipeline
Comprehensive test generation with coverage analysis.
claude-flow stream-chain pipeline testWorkflow Steps:
- Coverage Analysis: Identify areas lacking tests
- Test Design: Create test cases for critical functions
- Implementation: Generate unit tests with assertions
Use Cases:
- Increasing test coverage
- TDD workflow support
- Regression test creation
- Quality assurance
4. Optimize Pipeline
Performance optimization with profiling and implementation.
claude-flow stream-chain pipeline optimizeWorkflow Steps:
- Profiling: Identify performance bottlenecks
- Strategy: Analyze and suggest optimization approaches
- Implementation: Provide optimized code
Use Cases:
- Performance improvement
- Resource optimization
- Scalability enhancement
- Latency reduction
Pipeline Options
| Option | Description | Default |
--verbose | Show detailed execution | false |
--timeout <seconds> | Timeout per step | 30 |
--debug | Enable debug mode | false |
Pipeline Examples
Quick Analysis
claude-flow stream-chain pipeline analysisExtended Refactoring
claude-flow stream-chain pipeline refactor --timeout 60 --verboseDebug Test Generation
claude-flow stream-chain pipeline test --debugComprehensive Optimization
claude-flow stream-chain pipeline optimize --timeout 90 --verbosePipeline Output
Each pipeline execution provides:
- Progress: Step-by-step execution status
- Results: Success/failure per step
- Timing: Total and per-step execution time
- Summary: Consolidated results and recommendations
Custom Pipeline Definitions
Define reusable pipelines in .claude-flow/config.json:
Configuration Format
{
"streamChain": {
"pipelines": {
"security": {
"name": "Security Audit Pipeline",
"description": "Comprehensive security analysis",
"prompts": [
"Scan codebase for security vulnerabilities",
"Categorize issues by severity (critical/high/medium/low)",
"Generate fixes with priority and implementation steps",
"Create security test suite"
],
"timeout": 45
},
"documentation": {
"name": "Documentation Generation Pipeline",
"prompts": [
"Analyze code structure and identify undocumented areas",
"Generate API documentation with examples",
"Create usage guides and tutorials",
"Build architecture diagrams and flow charts"
]
}
}
}
}Execute Custom Pipeline
claude-flow stream-chain pipeline security
claude-flow stream-chain pipeline documentationAdvanced Use Cases
Multi-Agent Coordination
Chain different agent types for complex workflows:
claude-flow stream-chain run \
"Research best practices for API design" \
"Design REST API with discovered patterns" \
"Implement API endpoints with validation" \
"Generate OpenAPI specification" \
"Create integration tests" \
"Write deployment documentation"Data Transformation Pipeline
Process and transform data through multiple stages:
claude-flow stream-chain run \
"Extract user data from CSV files" \
"Normalize and validate data format" \
"Enrich data with external API calls" \
"Generate analytics report" \
"Create visualization code"Code Migration Workflow
Systematic code migration with validation:
claude-flow stream-chain run \
"Analyze legacy codebase dependencies" \
"Create migration plan with risk assessment" \
"Generate modernized code for high-priority modules" \
"Create migration tests" \
"Document migration steps and rollback procedures"Quality Assurance Chain
Comprehensive code quality workflow:
claude-flow stream-chain pipeline analysis
claude-flow stream-chain pipeline refactor
claude-flow stream-chain pipeline test
claude-flow stream-chain pipeline optimizeBest Practices
1. Clear and Specific Prompts
Good:
"Analyze authentication.js for SQL injection vulnerabilities"Avoid:
"Check security"2. Logical Progression
Order prompts to build on previous outputs:
1. "Identify the problem"
2. "Analyze root causes"
3. "Design solution"
4. "Implement solution"
5. "Verify implementation"3. Appropriate Timeouts
- Simple tasks: 30 seconds (default)
- Analysis tasks: 45-60 seconds
- Implementation tasks: 60-90 seconds
- Complex workflows: 90-120 seconds
4. Verification Steps
Include validation in your chains:
claude-flow stream-chain run \
"Implement feature X" \
"Write tests for feature X" \
"Verify tests pass and cover edge cases"5. Iterative Refinement
Use chains for iterative improvement:
claude-flow stream-chain run \
"Generate initial implementation" \
"Review and identify issues" \
"Refine based on issues found" \
"Final quality check"Integration with Claude Flow
Combine with Swarm Coordination
# Initialize swarm for coordination
claude-flow swarm init --topology mesh
# Execute stream chain with swarm agents
claude-flow stream-chain run \
"Agent 1: Research task" \
"Agent 2: Implement solution" \
"Agent 3: Test implementation" \
"Agent 4: Review and refine"Memory Integration
Stream chains automatically store context in memory for cross-session persistence:
# Execute chain with memory
claude-flow stream-chain run \
"Analyze requirements" \
"Design architecture" \
--verbose
# Results stored in .claude-flow/memory/stream-chain/Neural Pattern Training
Successful chains train neural patterns for improved performance:
# Enable neural training
claude-flow stream-chain pipeline optimize --debug
# Patterns learned and stored for future optimizationsTroubleshooting
Chain Timeout
If steps timeout, increase timeout value:
claude-flow stream-chain run "complex task" --timeout 120Context Loss
If context not flowing properly, use --debug:
claude-flow stream-chain run "step 1" "step 2" --debugPipeline Not Found
Verify pipeline name and custom definitions:
# Check available pipelines
cat .claude-flow/config.json | grep -A 10 "streamChain"Performance Characteristics
- Throughput: 2-5 steps per minute (varies by complexity)
- Context Size: Up to 100K tokens per step
- Memory Usage: ~50MB per active chain
- Concurrency: Supports parallel chain execution
Related Skills
- SPARC Methodology: Systematic development workflow
- Swarm Coordination: Multi-agent orchestration
- Memory Management: Persistent context storage
- Neural Patterns: Adaptive learning
Examples Repository
Complete Development Workflow
# Full feature development chain
claude-flow stream-chain run \
"Analyze requirements for user profile feature" \
"Design database schema and API endpoints" \
"Implement backend with validation" \
"Create frontend components" \
"Write comprehensive tests" \
"Generate API documentation" \
--timeout 60 \
--verboseCode Review Pipeline
# Automated code review workflow
claude-flow stream-chain run \
"Analyze recent git changes" \
"Identify code quality issues" \
"Check for security vulnerabilities" \
"Verify test coverage" \
"Generate code review report with recommendations"Migration Assistant
# Framework migration helper
claude-flow stream-chain run \
"Analyze current Vue 2 codebase" \
"Identify Vue 3 breaking changes" \
"Create migration checklist" \
"Generate migration scripts" \
"Provide updated code examples"Conclusion
Stream-Chain enables sophisticated multi-step workflows by:
- Sequential Processing: Each step builds on previous results
- Context Preservation: Full output history flows through chain
- Flexible Orchestration: Custom chains or predefined pipelines
- Agent Coordination: Natural multi-agent collaboration pattern
- Data Transformation: Complex processing through simple steps
Use run for custom workflows and pipeline for battle-tested solutions.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

