bootspring_orchestrator
Manage and execute multi-phase workflows with parallel agent coordination.
Overview#
The bootspring_orchestrator tool coordinates complex, multi-step workflows that span multiple agents, skills, and quality gates. It manages workflow state, handles phase transitions, generates parallel execution plans, and ensures proper sequencing of tasks.
New in v2.3.4: The plan action generates structured multi-phase execution plans that Claude Code and other MCP clients can follow to spawn parallel agents automatically.
Parameters#
| Parameter | Type | Required | Description |
|---|---|---|---|
action | string | Yes | analyze, suggest, recommend, workflows, workflow, start, next, checkpoint, status, plan |
context | string | For analyze/suggest/plan | Task description to analyze |
workflow | string | Conditional | Workflow name (for workflow/start/plan) |
signal | string | For checkpoint | Completion signal reference |
limit | number | No | Max recommendations for recommend action (default: 5, max: 50) |
mode | string | No | Entitlement mode: local or server |
tier | string | No | Tier override: free, pro, team, enterprise |
Available Workflows#
Development Workflows#
| Workflow | Description | Phases |
|---|---|---|
feature-development | End-to-end feature building | Plan → Design → Implement → Test → Review |
database-migration | Safe database migrations | Backup → Migrate → Validate → Rollback-Ready |
security-audit | Comprehensive security review | Scan → Analyze → Report → Remediate |
performance-optimization | Performance improvement | Profile → Identify → Optimize → Verify |
Launch Pack (Pro)#
| Workflow | Description |
|---|---|
launch/pre-launch | Pre-launch checklist |
launch/waitlist | Waitlist implementation |
launch/landing-page | Landing page creation |
launch/launch-day | Launch day execution |
launch/post-launch | Post-launch optimization |
Fundraising Pack (Pro)#
| Workflow | Description |
|---|---|
fundraising/readiness | Fundraising readiness assessment |
fundraising/materials | Pitch materials preparation |
fundraising/targeting | Investor targeting |
fundraising/pitching | Pitch meeting framework |
fundraising/closing | Deal closing process |
Growth Pack (Pro)#
| Workflow | Description |
|---|---|
growth/pmf | Product-market fit measurement |
growth/metrics | Metrics dashboard setup |
growth/acquisition | User acquisition strategy |
growth/retention | Retention optimization |
Enterprise Pack (Team)#
| Workflow | Description |
|---|---|
enterprise/readiness | Enterprise feature readiness |
enterprise/sales | Enterprise sales process |
enterprise/security | Security compliance |
enterprise/implementation | Enterprise onboarding |
Usage Examples#
Generate a Parallel Execution Plan (NEW)#
The plan action is the fastest way to launch a massive multi-agent workflow. It analyzes your task, selects the best workflow template, and returns a structured plan with parallel agent groups.
Use the bootspring_orchestrator tool with:
- action: "plan"
- context: "Full production audit - security gaps, broken pages, workflow issues, connection problems"
Response:
Claude Code reads this plan and spawns parallel agents for each phase. Each agent calls bootspring_agent invoke for specialist expertise and bootspring_skill search for code patterns.
With explicit workflow:
Use the bootspring_orchestrator tool with:
- action: "plan"
- workflow: "full-stack-parallel"
- context: "Build a dashboard with real-time analytics"
Custom plan (no matching workflow):
Use the bootspring_orchestrator tool with:
- action: "plan"
- context: "Build payment checkout with Stripe subscriptions and webhook handling"
When no workflow matches, the orchestrator builds a custom plan from agent routing based on keyword analysis.
Start a Workflow#
Use the bootspring_orchestrator tool with:
- action: "start"
- workflow: "feature-development"
- params: { feature: "user notifications", requirements: "email, push, in-app" }
Response:
Check Workflow Status#
Use the bootspring_orchestrator tool with:
- action: "status"
- workflowId: "wf_abc123"
Response:
Resume a Paused Workflow#
Use the bootspring_orchestrator tool with:
- action: "resume"
- workflowId: "wf_abc123"
Pause a Workflow#
Use the bootspring_orchestrator tool with:
- action: "pause"
- workflowId: "wf_abc123"
List Active Workflows#
Use the bootspring_orchestrator tool with:
- action: "list"
Response:
Workflow Phases#
Feature Development Workflow#
┌──────────┐ ┌──────────┐ ┌────────────┐ ┌──────────┐ ┌──────────┐
│ Plan │───>│ Design │───>│ Implement │───>│ Test │───>│ Review │
│ │ │ │ │ │ │ │ │ │
│ • Goals │ │ • Schema │ │ • Backend │ │ • Unit │ │ • Code │
│ • Scope │ │ • API │ │ • Frontend │ │ • E2E │ │ • Security│
│ • Agents │ │ • UI/UX │ │ • Skills │ │ • Integr │ │ • Quality │
└──────────┘ └──────────┘ └────────────┘ └──────────┘ └──────────┘
Phase Agents#
Each phase uses specific agents:
| Phase | Primary Agent | Supporting Agents |
|---|---|---|
| Plan | architecture-expert | product-expert |
| Design | database-expert, api-expert | ui-ux-expert |
| Implement | backend-expert, frontend-expert | - |
| Test | testing-expert | - |
| Review | security-expert, code-review-expert | - |
Workflow Artifacts#
Workflows produce artifacts saved in .bootspring/workflows/:
.bootspring/
└── workflows/
└── wf_abc123/
├── state.json # Workflow state
├── plan.md # Phase 1 output
├── design.md # Phase 2 output
├── implement/ # Phase 3 artifacts
│ ├── files.json # Created/modified files
│ └── log.md # Implementation log
├── test/ # Phase 4 artifacts
│ ├── results.json # Test results
│ └── coverage.json # Coverage report
└── review/ # Phase 5 artifacts
├── security.md # Security review
└── quality.md # Quality report
Configuration#
Workflow Customization#
Checkpoint Behavior#
Error Handling#
Phase Failure#
When a phase fails:
- Workflow pauses automatically (if
pauseOnFailure: true) - Error details are saved to artifacts
- Options provided for:
- Retry the phase
- Skip the phase
- Cancel the workflow
Recovery#
Use the bootspring_orchestrator tool with:
- action: "resume"
- workflowId: "wf_abc123"
- options: { retryFailed: true }
Parallel Execution#
Some workflow phases can run in parallel:
Best Practices#
1. Start with Built-in Workflows#
Use existing workflows before creating custom ones.
2. Review Phase Outputs#
Check artifacts between phases to ensure quality.
3. Use Checkpoints#
Enable checkpoints for long-running workflows.
4. Handle Failures Gracefully#
Configure pauseOnFailure to review issues before continuing.
Related Tools#
bootspring_agent- Agent invocationbootspring_quality- Quality gatesbootspring_loop- Autonomous execution