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:
1{
2 "workflowId": "wf_abc123",
3 "workflow": "feature-development",
4 "status": "running",
5 "currentPhase": "build",
6 "phases": [
7 { "name": "plan", "status": "completed", "duration": 180000 },
8 { "name": "design", "status": "completed", "duration": 240000 },
9 { "name": "build", "status": "in_progress", "startedAt": "..." },
10 { "name": "test", "status": "pending" },
11 { "name": "review", "status": "pending" }
12 ],
13 "params": {
14 "feature": "user notifications",
15 "requirements": "email, push, in-app"
16 },
17 "checkpoints": ["plan", "design"],
18 "artifacts": [
19 { "type": "plan", "path": "plan.md" },
20 { "type": "design", "path": "design.md" }
21 ]
22}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:
1// bootspring.config.js
2module.exports = {
3 workflows: {
4 'feature-development': {
5 phases: [
6 { name: 'plan', agent: 'architecture-expert' },
7 { name: 'design', agents: ['database-expert', 'api-expert'] },
8 {
9 name: 'build',
10 parallel: true,
11 tasks: [
12 { agent: 'backend-expert', task: 'Build API' },
13 { agent: 'frontend-expert', task: 'Build UI' },
14 ],
15 },
16 { name: 'test', agent: 'testing-expert' },
17 { name: 'review', agents: ['security-expert', 'code-review-expert'] },
18 ],
19 },
20 },
21};Quality Gates#
Workflows can include quality gates between phases:
Plan ──> Design ──> Build ──┬──> Test ──┬──> Review
│ │
pre-commit pre-push
gate gate
Configure gates:
1module.exports = {
2 workflows: {
3 'feature-development': {
4 qualityGates: {
5 build: 'pre-commit', // Run before leaving build phase
6 test: 'pre-push', // Run before leaving test phase
7 review: 'pre-deploy', // Run before deployment
8 },
9 },
10 },
11};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
1{
2 "status": "paused",
3 "error": {
4 "phase": "test",
5 "message": "Test coverage below threshold",
6 "details": {
7 "actual": 72,
8 "required": 80
9 }
10 },
11 "options": ["retry", "skip", "cancel"]
12}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:
1module.exports = {
2 workflows: {
3 'feature-development': {
4 phases: [
5 'plan',
6 'design',
7 'implement',
8 'test',
9 'review',
10 'deploy', // Added deployment phase
11 ],
12 agents: {
13 deploy: 'devops-expert',
14 },
15 },
16 },
17};Skip Phases#
Skip specific phases:
1module.exports = {
2 workflows: {
3 'feature-development': {
4 skipPhases: ['review'], // Skip review for quick iterations
5 },
6 },
7};Custom Workflows#
Create your own workflow:
1module.exports = {
2 workflows: {
3 'api-feature': {
4 description: 'Build an API feature',
5 phases: [
6 { name: 'design', agent: 'api-expert' },
7 { name: 'schema', agent: 'database-expert' },
8 { name: 'implement', agent: 'backend-expert' },
9 { name: 'test', agent: 'testing-expert' },
10 { name: 'document', agent: 'content-expert' },
11 ],
12 },
13 },
14};Checkpoints#
Workflows save checkpoints for recovery:
1module.exports = {
2 workflows: {
3 checkpoints: {
4 frequency: 'phase', // Save after each phase
5 retention: 7, // Keep for 7 days
6 autoRestore: true, // Auto-restore on resume
7 },
8 },
9};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