Main conductor for unified workflow - orchestrates workflow stages
Auto-activates when:
/workflow:start-development-workflowThe orchestrator manages a unified workflow with three sequential stages. Based on complexity, stages can be:
┌─────────────────────────────────────────┐
│ WORKFLOW ORCHESTRATOR │
└─────────────────────────────────────────┘
↓
┌─────────────────────────────────────────┐
│ STAGE A: SPECIFICATION STAGE │
│ - Analyze requirements │
│ - Create spec (SDD + OpenSpec) │
│ - Validate with PoC (if complex) │
└─────────────────────────────────────────┘
↓
┌─────────────────────────────────────────┐
│ STAGE B: DEVELOPMENT STAGE │
│ - Define behaviors (BDD scenarios) │
│ - Test-driven implementation (TDD) │
│ - Iterative refinement │
└─────────────────────────────────────────┘
↓
┌─────────────────────────────────────────┐
│ STAGE C: EXECUTION STAGE │
│ - Task tracking (if available) │
│ - Implementation execution │
│ - Verification & completion │
└─────────────────────────────────────────┘
Triggers:
15 steps estimated
Workflow:
Stage A: FULL
├─ Research existing system
├─ Create comprehensive spec (OpenSpec if available)
├─ Generate PoC validation tests
└─ Manual validation questions
Stage B: FULL
├─ Define BDD scenarios for all features
├─ TDD implementation (RED-GREEN-REFACTOR)
└─ Continuous spec updates
Stage C: FULL
├─ Create tasks (if task-management exists)
├─ Track progress per task
└─ Comprehensive verification
Triggers:
Workflow:
Stage A: SIMPLIFIED
├─ Review existing spec
├─ Create spec change document
└─ Skip PoC validation
Stage B: FULL
├─ Define BDD scenarios
├─ TDD implementation
└─ Update spec as needed
Stage C: SIMPLIFIED
├─ Optional task tracking
└─ Standard verification
Triggers:
Workflow:
Stage A: SKIP
└─ No formal spec needed
Stage B: SIMPLIFIED
├─ Write tests directly (TDD)
└─ Implement
Stage C: MINIMAL
└─ Quick verification
User: /workflow:start-development-workflow "Add user authentication"
Orchestrator:
1. Analyze request
2. Detect complexity → COMPLEX
3. Check integrations:
- ✓ task-management available
- ✓ openspec/ directory found
4. Prepare workflow plan
Complex:
→ Invoke: /workflow:create-workflow-spec-stage --mode=full
1. Research phase
2. Create OpenAPI spec (using OpenSpec format)
3. Generate PoC tests (invoke meta-validator agent)
4. Manual validation questions
5. Get user approval
Medium:
→ Invoke: /workflow:create-workflow-spec-stage --mode=light
1. Review existing spec
2. Create spec change document
3. Get user approval
Simple:
→ Skip Stage A entirely
Complex/Medium:
→ Invoke: /workflow:dev-stage --mode=full
1. Generate BDD scenarios from spec
- Use /workflow:behavior-driven
2. For each scenario:
- Write failing test (RED)
- Implement feature (GREEN)
- Refactor (REFACTOR)
- Use /workflow:test-driven
3. Update spec as you learn
- Use /workflow:openspec-integration
Simple:
→ Invoke: /workflow:dev-stage --mode=simple
1. Write tests directly (TDD)
2. Implement
3. Refactor
Complex:
→ Invoke: /workflow:exec-stage --mode=full
1. Create tasks (if task-management exists)
- Use /workflow:task-integration
2. For each task:
- Mark in_progress
- Execute
- Mark completed
3. Comprehensive verification
4. Final review
Medium:
→ Invoke: /workflow:exec-stage --mode=standard
1. Optional task tracking
2. Execute implementation
3. Standard verification
Simple:
→ Invoke: /workflow:exec-stage --mode=minimal
1. Run tests
2. Quick verification
3. Done
if [ -d "openspec/" ]; then
USE_OPENSPEC=true
BLOCK_A_FORMAT="openspec"
fi
if task-management plugin exists; then
USE_TASKS=true
BLOCK_C_TRACKING="task-based"
fi
For Stage A:
- Use /workflow:create-workflow-spec-driven-development
- Create OpenAPI/AsyncAPI specs
For Stage B:
- Use /workflow:behavior-driven
- Generate Given-When-Then scenarios
For Stage B:
- Use /workflow:test-driven-development
- RED-GREEN-REFACTOR cycle
Track workflow state in .claude/workflow-state.md:
---
workflow_id: WF-2026-02-09-001