AgentFlow SDLC v0.7.0 — Multi-Agent Efficiency and SDLC Patterns
This minor release introduces formal patterns for multi-agent workflows, drastically improving efficiency while preserving durable compliance. It also expands the framework's documentation to explicitly map its core tenets and rule sets.
What's New
Multi-Agent Efficiency Patterns
- Dual-Write Handoffs: The Orchestrator now uses local scratch files (.agent-runs/scratch/SDD-.md) for heavy technical design documentation while simultaneously posting compliance summaries to the GitHub issue. This saves significant token context and time on network round trips.
- Architectural Sprints: Batch orchestration commands are now formalized as Architectural Sprints. The Architect phase evaluates the entire batch collectively before implementation begins.
- Opt-In Design Gates: Introduced an explicit pause step after the Architect phase for high-assurance work or explicit prompts, enforcing human review of the Solution Design Document before code is written.
- Sub-Agent Role Templates: Added isolated
ole-architect.md and
ole-implementer.md templates to provide strict boundaries during phase handoffs.
Documentation and Core Principles
- Core Tenets Matrix: The README now explicitly maps SDLC challenges to AgentFlow capabilities and solutions.
- Human/Agent Parity: Documented the strict rule that human and agent contributors must follow the exact same issue/PR contract.
- Unambiguous Issue Standards: Updated issue templates and standards to clearly separate Background & Problem from Technical Design.
- Lifecycle Flowchart: Added a Mermaid diagram to the README mapping the end-to-end issue workflow.
Upgrade Guidance
Existing projects can sync these updates and receive the new issue templates and orchestrator behaviors:
bash node /path/to/agentflow-sdlc/bin/cli.mjs sync --target .