// Use and customize workflow templates for common scenarios. Use when user wants to use a template, asks about available templates, or wants to customize existing workflows.
Use when user says "create workflow", "create a workflow", "design workflow", "orchestrate", "automate multiple steps", "coordinate agents", "multi-agent workflow". Creates orchestration workflows from natural language using Socratic questioning to plan multi-agent workflows with visualization.
Use when user provides workflow syntax with arrows (-> || ~>), says "run workflow", "execute workflow", "run this", mentions step1 -> step2 patterns. Executes orchestration workflows with real-time visualization, steering, and error recovery.
Manages temporary and defined agents including creation, promotion, cleanup, and namespacing. Use when user creates custom agents, asks about agent lifecycle, temp agents, or agent management.
Debug workflow execution issues including syntax errors, agent failures, variable problems, and execution errors. Use when workflows fail, produce unexpected results, or user asks for debugging help.
Design custom syntax elements with reuse-first approach for workflow orchestration. Use when user needs custom operators, checkpoints, or syntax patterns not available in core syntax.
Create and execute temporary scripts (Python, Node.js, shell) during workflow execution for API integrations, data processing, and custom tools. Use when user needs to interact with external APIs, process data with specific libraries, or create temporary executable code.
| name | using-templates |
| description | Use and customize workflow templates for common scenarios. Use when user wants to use a template, asks about available templates, or wants to customize existing workflows. |
I help you use and customize workflow templates for common automation scenarios.
I activate when you:
Templates are searched in the following locations (in order of priority):
./workflows/*.flow - Project-specific templates~/.claude/workflows/*.flow - User's global templates~/.claude/plugins/repos/orchestration/examples/*.flow - Built-in examplesProject-local templates take precedence over global templates.
Located in examples/ directory:
# List project templates
ls ./workflows/*.flow 2>/dev/null
# List user's global templates
ls ~/.claude/workflows/*.flow 2>/dev/null
# List built-in examples
ls ~/.claude/plugins/repos/orchestration/examples/*.flow
# View from any location
cat ./workflows/my-template.flow
cat ~/.claude/workflows/my-template.flow
cat ~/.claude/plugins/repos/orchestration/examples/tdd-implementation.flow
Use /orchestration:template command (searches all locations automatically):
/orchestration:template tdd-implementation
Or reference directly with path:
Use ./workflows/my-workflow.flow
Use ~/.claude/workflows/my-workflow.flow
Use examples/tdd-implementation.flow
Some templates have parameters:
# Template with parameter
$scanner := {base: "Explore", prompt: "{{SCAN_TYPE}}", model: "sonnet"}
Customize:
# Your version
$scanner := {base: "Explore", prompt: "Security expert", model: "sonnet"}
Add or remove workflow steps:
# Original
step1 -> step2 -> step3
# Your version (added error handling)
step1 -> step2 ->
(if failed)~> handle-error ~>
(if passed)~> step3
Insert review points:
# Original
analyze -> implement -> deploy
# Your version
analyze -> implement -> @review-implementation -> deploy
Templates typically have:
# Header with description
# Template: TDD Implementation
# Description: Implement features using Test-Driven Development
# Parameters: None
# Phase 1: RED
step1 -> step2
# Phase 2: GREEN
step3 -> step4
# Phase 3: REFACTOR
step5 -> step6
After customizing, save to your preferred location:
mkdir -p ./workflows
cat > ./workflows/my-project-workflow.flow << 'EOF'
# My Project Workflow
# Description: Custom automation for this project
...
EOF
mkdir -p ~/.claude/workflows
cat > ~/.claude/workflows/my-global-workflow.flow << 'EOF'
# My Global Workflow
# Description: Custom automation available everywhere
...
EOF
cat > ~/.claude/plugins/repos/orchestration/examples/my-workflow.flow << 'EOF'
# My Example Workflow
# Description: Custom automation for X
...
EOF
Guidelines:
.flow extension✅ DO:
❌ DON'T:
Common parameters in templates:
| Parameter | Purpose | Example |
|---|---|---|
{{TARGET}} | Target file/directory | src/components |
{{SCAN_TYPE}} | Type of scan | security, performance |
{{ENV}} | Environment | staging, production |
{{BRANCH}} | Git branch | main, develop |
Want to use a template? Ask me to show available templates or execute one!