Overview
Integrate BAML (Basically a Made-up Language) framework to replace ad-hoc prompt engineering with type-safe, schema-validated LLM interactions across all 5 AutoSDLC agents.
Problem Statement
Current Phase 3 implementation relies on:
- Ad-hoc prompt engineering in agent tools
- Mock implementations without schema validation
- Manual string manipulation for agent communication
- Limited multi-model flexibility
Solution: BAML Integration
BAML provides:
- Type-safe prompt engineering with schema validation
- Multi-model support with easy switching/fallbacks
- Structured agent coordination via validated schemas
- VSCode integration for prompt debugging
- Streaming and tool-calling for complex workflows
Implementation Plan
Phase 1: Foundation (Week 1)
Phase 2: Agent Integration (Week 2)
Phase 3: Enhancement (Week 3)
Integration with Existing Issues
This enhancement amplifies existing Phase 3 work:
Success Metrics
Dependencies
- Must integrate with existing Phase 3 tracks
- Requires updates to documentation and existing issues
- Compatible with current TDD approach and testing framework
This is a foundational enhancement that makes all other Phase 3 work more robust and maintainable.
Overview
Integrate BAML (Basically a Made-up Language) framework to replace ad-hoc prompt engineering with type-safe, schema-validated LLM interactions across all 5 AutoSDLC agents.
Problem Statement
Current Phase 3 implementation relies on:
Solution: BAML Integration
BAML provides:
Implementation Plan
Phase 1: Foundation (Week 1)
@boundaryml/baml,@boundaryml/baml-cli)baml_src/directory with schema definitionsPhase 2: Agent Integration (Week 2)
Phase 3: Enhancement (Week 3)
Integration with Existing Issues
This enhancement amplifies existing Phase 3 work:
Success Metrics
Dependencies
This is a foundational enhancement that makes all other Phase 3 work more robust and maintainable.