Workflows
Workflows orchestrate complex, multi-step processes that span multiple agents, skills, and quality gates. They coordinate everything from feature development to product launches.
How Workflows Work
Workflows break complex tasks into phases, each handled by specialized agents:
┌──────────────────────────────────────────────────────────────────────────┐
│ Workflow Execution │
├──────────────────────────────────────────────────────────────────────────┤
│ │
│ Phase 1 Phase 2 Phase 3 Phase 4 Phase 5 │
│ ┌──────┐ ┌──────┐ ┌──────┐ ┌──────┐ ┌──────┐ │
│ │ Plan │──────>│Design│──────>│Build │──────>│ Test │──────>│Review│ │
│ └──────┘ └──────┘ └──────┘ └──────┘ └──────┘ │
│ │ │ │ │ │ │
│ ▼ ▼ ▼ ▼ ▼ │
│ ┌──────┐ ┌──────┐ ┌──────┐ ┌──────┐ ┌──────┐ │
│ │Archi-│ │Data- │ │Back- │ │Test- │ │Secu- │ │
│ │tect │ │base │ │end │ │ing │ │rity │ │
│ │Expert│ │Expert│ │Expert│ │Expert│ │Expert│ │
│ └──────┘ └──────┘ └──────┘ └──────┘ └──────┘ │
│ │
│ ═══════════════════════════════════════════════════════════════════ │
│ Checkpoints Artifacts State Quality Gates │
│ │
└──────────────────────────────────────────────────────────────────────────┘
Workflow Categories
Development Workflows (Free)
Core development processes:
| Workflow | Description | Phases |
|---|---|---|
feature-development | End-to-end feature building | Plan → Design → Build → Test → Review |
database-migration | Safe schema changes | Backup → Migrate → Validate → Rollback-Ready |
security-audit | Comprehensive security review | Scan → Analyze → Report → Remediate |
performance-optimization | Performance improvement | Profile → Identify → Optimize → Verify |
code-refactor | Structured refactoring | Analyze → Plan → Refactor → Test |
bug-investigation | Systematic debugging | Reproduce → Analyze → Fix → Verify |
Launch Pack (Pro)
Product launch workflows:
| Workflow | Description |
|---|---|
launch/pre-launch | Pre-launch checklist and validation |
launch/waitlist | Waitlist implementation |
launch/landing-page | Landing page creation |
launch/launch-day | Launch day execution plan |
launch/post-launch | Post-launch optimization |
Fundraising Pack (Pro)
Fundraising workflows:
| Workflow | Description |
|---|---|
fundraising/readiness | Assess fundraising readiness |
fundraising/materials | Pitch deck and materials |
fundraising/targeting | Investor targeting strategy |
fundraising/pitching | Pitch meeting framework |
fundraising/closing | Deal closing process |
Growth Pack (Pro)
Growth-focused workflows:
| Workflow | Description |
|---|---|
growth/pmf | Product-market fit measurement |
growth/metrics | Metrics dashboard setup |
growth/acquisition | User acquisition strategy |
growth/retention | Retention optimization |
growth/monetization | Monetization strategy |
Enterprise Pack (Team)
Enterprise workflows:
| Workflow | Description |
|---|---|
enterprise/readiness | Enterprise feature assessment |
enterprise/sales | Enterprise sales process |
enterprise/security | Security compliance (SOC2, HIPAA) |
enterprise/implementation | Enterprise onboarding |
Using Workflows
Starting a Workflow
Start the feature-development workflow to build user notifications
with email, push, and in-app delivery.
The orchestrator will:
- Create a workflow instance
- Start the first phase
- Coordinate agents through each phase
- Track progress and artifacts
Checking Status
What's the status of my current workflow?
Shows:
- Current phase and progress
- Completed phases
- Generated artifacts
- Any blockers or issues
Pausing and Resuming
Pause the current workflow.
Resume workflow wf_abc123.
Workflows maintain state and can be paused/resumed anytime.
Workflow Phases in Detail
Feature Development Workflow
Phase 1: Plan
├── Agent: architecture-expert
├── Output: plan.md
└── Contains:
├── Feature scope and goals
├── Component breakdown
├── Technical approach
└── Agents to involve
Phase 2: Design
├── Agents: database-expert, api-expert, ui-ux-expert
├── Output: design.md
└── Contains:
├── Database schema
├── API surface
├── UI mockups/wireframes
└── Data flow diagrams
Phase 3: Build
├── Agents: backend-expert, frontend-expert
├── Output: implement/
└── Contains:
├── Source code files
├── Database migrations
├── Implementation log
└── Files created/modified list
Phase 4: Test
├── Agent: testing-expert
├── Output: test/
└── Contains:
├── Unit tests
├── Integration tests
├── E2E tests
├── Test results
└── Coverage report
Phase 5: Review
├── Agents: security-expert, code-review-expert
├── Output: review/
└── Contains:
├── Security assessment
├── Code quality report
├── Recommendations
└── Final checklist
Database Migration Workflow
Phase 1: Backup
├── Create database snapshot
├── Document current schema
└── Verify backup integrity
Phase 2: Migrate
├── Generate migration files
├── Run migrations on staging
└── Validate data integrity
Phase 3: Validate
├── Run test suite
├── Check query performance
└── Verify data consistency
Phase 4: Rollback-Ready
├── Create rollback script
├── Document rollback process
└── Test rollback procedure
Security Audit Workflow
Phase 1: Scan
├── Dependency vulnerability scan
├── Static code analysis
├── Secrets detection
└── Configuration review
Phase 2: Analyze
├── Risk assessment
├── Attack surface mapping
├── Compliance check
└── Prioritization
Phase 3: Report
├── Executive summary
├── Detailed findings
├── Severity ratings
└── Remediation timeline
Phase 4: Remediate
├── Fix critical issues
├── Update dependencies
├── Implement recommendations
└── Re-scan verification
Workflow Artifacts
All workflows produce artifacts saved in .bootspring/workflows/:
.bootspring/
└── workflows/
└── wf_abc123/
├── state.json # Workflow state
├── plan.md # Phase 1: Planning document
├── design.md # Phase 2: Design specifications
├── implement/ # Phase 3: Implementation
│ ├── files.json # Created/modified files
│ └── log.md # Implementation decisions
├── test/ # Phase 4: Testing
│ ├── results.json # Test results
│ └── coverage.json # Coverage metrics
└── review/ # Phase 5: Review
├── security.md # Security findings
└── quality.md # Code quality report
State Tracking
Each workflow maintains state:
Loading code block...
Parallel Execution
Some phases can run in parallel:
┌─────────────────────────────────────────────────────────────┐
│ Feature Development │
├─────────────────────────────────────────────────────────────┤
│ │
│ Plan ──────> Design ──────> Build ──────> Test ──> Review │
│ │ │ │
│ │ │ (parallel) │
│ │ │ │
│ ┌──────┴──┴──────┐ │
│ │ │ │
│ Backend Frontend │
│ (backend- (frontend- │
│ expert) expert) │
│ │ │ │
│ └───────┬────────┘ │
│ │ │
│ Integration │
│ │
└─────────────────────────────────────────────────────────────┘
Configure parallel phases:
Loading code block...
Quality Gates
Workflows can include quality gates between phases:
Plan ──> Design ──> Build ──┬──> Test ──┬──> Review
│ │
pre-commit pre-push
gate gate
Configure gates:
Loading code block...
Error Handling
Phase Failures
When a phase fails:
- Workflow pauses automatically
- Error details are saved
- Options presented:
- Retry - Run the phase again
- Skip - Move to next phase
- Cancel - Stop the workflow
Loading code block...
Recovery
Resume with retry:
Resume workflow wf_abc123 and retry the failed phase.
Skip and continue:
Resume workflow wf_abc123 and skip the failed phase.
Customizing Workflows
Custom Phases
Add or modify phases:
Loading code block...
Skip Phases
Skip specific phases:
Loading code block...
Custom Workflows
Create your own workflow:
Loading code block...
Checkpoints
Workflows save checkpoints for recovery:
Loading code block...
Manual Checkpoints
Create a checkpoint for the current workflow.
Restoring from Checkpoint
Restore workflow wf_abc123 to the design phase checkpoint.
Workflow Best Practices
1. Start with Built-in Workflows
Use existing workflows before creating custom ones:
feature-developmentfor most featuressecurity-auditbefore launchesperformance-optimizationfor speed issues
2. Review Phase Outputs
Check artifacts between phases:
- Read
plan.mdbefore design - Verify schema in
design.mdbefore building - Review test results before final review
3. Use Quality Gates
Enable gates for critical workflows:
pre-commitcatches obvious issuespre-pushvalidates tests passpre-deployensures production readiness
4. Handle Failures Gracefully
Don't skip failures without understanding:
- Review error details
- Fix underlying issues
- Re-run the phase
5. Keep Workflows Focused
One workflow, one goal:
- Don't combine unrelated tasks
- Break large features into multiple workflows
- Use workflow chaining for dependencies
Tier Access
| Tier | Workflows Available |
|---|---|
| Free | Development workflows (6) |
| Pro | Free + Launch, Fundraising, Growth packs |
| Team | Pro + Enterprise pack + Custom workflows |
| Enterprise | All + Unlimited custom |
Related
- Workflows Introduction - Getting started guide
- bootspring_orchestrator - Tool reference
- Orchestrator - Engine details
- Quality Gates - Gate configuration