creating-workflows-from-description

# Creating Workflows from Description

## When to Use

Proactively suggest orchestration when user describes tasks involving:

- **Multiple sequential steps** with dependencies
- **Parallel operations** that could run simultaneously
- **Conditional logic** or branching (if/then scenarios)
- **Error handling** or retry requirements
- **Testing, review, and deployment** phases
- **Complex multi-agent coordination**
- **Quality gates** or approval checkpoints

## Trigger Patterns

Watch for these patterns in user messages:

**Explicit workflow requests:**
- "I need to [multi-step task]"
- "Help me build a pipeline for [process]"
- "Create a workflow that [description]"
- "Automate [complex task]"

**Implicit workflow descriptions:**
- User describes 3+ sequential steps
- User mentions temporal ordering: "then", "after that", "once that's done"
- User mentions conditionals: "if that works", "if tests pass"
- User mentions parallel work: "at the same time", "in parallel", "simultaneously"
- User mentions reviews/approvals: "needs review", "after approval"
- User mentions retry/error handling: "if it fails", "retry", "rollback"

**Example phrases:**
- "run tests, then if they pass..."
- "deploy to production after security review"
- "implement with TDD workflow"
- "check code quality before merging"
- "parallel test execution"

## Action

When triggers detected, suggest orchestration:

```
This sounds like a perfect use case for orchestration! I can help you create a workflow that handles:

[List 2-4 key aspects identified from description, e.g.:]
- Sequential testing and deployment steps
- Parallel validation (tests + security scan)
- Conditional deployment based on test results
- Automatic rollback on failure

Would you like me to guide you through creating this workflow?
```

**If user says yes:**

Execute the create command with their description:
```
/orchestration:create [initial description from user message]
```

**If user says no or wants to see example first:**