Building with Workflows
A practical guide to using Bootspring workflows for efficient development
This guide shows you how to effectively use Bootspring workflows for your development process, from simple features to complex releases.
Understanding Workflows#
Workflows are structured development processes that:
- Guide you through phases with the right agents
- Track progress with completion signals
- Ensure quality with best practices at each step
Choosing the Right Workflow#
For New Features#
Use Feature Development for most new functionality:
This workflow guides you through:
- Design - Plan the feature with ui-ux-expert and api-expert
- Implementation - Build with backend/frontend experts
- Testing - Verify with testing-expert
- Review - Final check with security/performance experts
For Bug Fixes#
For small fixes, you might not need a full workflow. But for significant bugs:
For Security Work#
Use Security Audit for security-focused work:
For Performance Work#
Use Performance Optimization:
For Releases#
Use Launch Preparation before deploying:
Workflow Lifecycle#
Starting#
Working Through Phases#
Each phase has recommended agents. Invoke them:
Advancing#
When a phase is complete:
Tracking Signals#
Mark completion signals as you achieve them:
Completing#
When all phases are done:
Practical Example: Building User Authentication#
1. Start the Workflow#
2. Design Phase#
Outputs:
- API contract for auth endpoints
- UI mockups for auth screens
- Database schema for users
3. Move to Implementation#
4. Implementation Phase#
5. Move to Testing#
6. Testing Phase#
7. Move to Review#
8. Review Phase#
9. Complete#
Using Parallel Execution#
For independent work, use parallel workflows:
Backend and frontend development happen simultaneously:
Handling Failures#
If something goes wrong:
Chaining Workflows#
For complex processes, use composition:
Best Practices#
1. Start with the Right Workflow#
Don't over-engineer small tasks, but don't skip workflows for complex work.
2. Use Agents at Each Phase#
The recommended agents exist for a reason. Invoke them.
3. Track Your Signals#
Completion signals help you know when phases are truly done.
4. Handle Failures Properly#
Use the remediation system instead of abandoning workflows.
5. Review Your History#
Learn from past workflows to improve your process.
Quick Reference#
| Command | Description |
|---|---|
workflow start <name> | Start a workflow |
workflow next | Advance to next phase |
workflow status | Check current status |
workflow signals | List completion signals |
workflow checkpoint <signal> | Mark signal complete |
workflow pause | Pause the workflow |
workflow resume | Resume paused workflow |
workflow report-failure <type> | Report a failure |