Reduced lead time with inspectable workflows
Agents executed cross-repo tasks while humans maintained intent.
Context
An engineering team managing multiple interconnected repositories, struggling with coordination overhead on cross-cutting changes.
Constraints
Financial services compliance required full audit trails. Every change needed documented approval chain.
Before
Cross-repo changes required manual coordination across teams, often taking days to propagate through all systems.
After
Agents coordinate changes across repos while maintaining proper sequencing. Humans approve the overall intent, agents handle execution.
What Agents Do
Identify affected repositories, create coordinated PRs, update Linear tickets, notify relevant team members.
What Humans Do
Define the change intent, review agent proposals, approve final changes.
Receipts
$ agent run change:propagate --scope=auth-update
✓ analyzed dependency graph
✓ identified 4 affected repositories
✓ created PRs in api-service, web-client, mobile-app, shared-types
✓ linked Linear tickets
✓ notified @platform-team in SlackThe Challenge
Cross-repository changes were a coordination nightmare. A single API change might require updates in:
- The core API service
- The web client
- Mobile applications
- Shared type definitions
Each update needed to happen in the right order, with proper testing and approvals.
The Solution
We built agent workflows that understand the dependency relationships between repositories and can coordinate changes automatically.
The agent analyzes the impact of a proposed change, creates properly sequenced pull requests, and keeps all tracking systems in sync. Humans define what needs to change; agents figure out how to propagate it safely.
Results
Lead time for cross-cutting changes dropped significantly. More importantly, the team now has confidence that changes propagate correctly, with full visibility into every step.
Ready to build something similar?
Let's discuss how we can create inspectable, human-friendly workflows for your team.