I design how agents
work together.
Context engineering establishes shared understanding. Specification-driven development turns intent into executable work. Multi-agent orchestration coordinates delivery. I direct the product decisions and use integration evidence to refine the system.
Knowledge that develops
with the product.
Product intent, domain contracts, and architectural decisions guide each assignment. Integration findings feed back into that shared knowledge and the next wave.
Scroll horizontally to explore the diagram. Playback controls are below.
01 SpecifyMichael turns shared product knowledge and decisions into a specification packet for each agent.
From intent to integrated work.
Persistent product knowledge connects the cycle. Each wave draws on the decisions already made, produces integrated software, and contributes evidence for the next set of decisions.
Build the shared context
Context engineeringCapture product intent, domain rules, architectural decisions, and constraints in version-controlled knowledge.
Specify the work
Specification-driven developmentDefine bounded assignments with dependencies, shared contracts, ownership, and acceptance criteria.
Orchestrate parallel execution
Multi-agent orchestrationAssign independent work concurrently and sequence changes that share dependencies.
Integrate and verify
Integration gatesEvaluate the combined product through automated checks and end-to-end workflows.
Update the knowledge and the plan
Persistent memory · feedback-driven replanningIncorporate findings into specifications, reusable instructions, and subsequent waves.
Where I apply judgment.
Product: which problems deserve investment and what success means.
Architecture: which decisions must hold across the platform.
Execution: what can run concurrently and where integration belongs.
Economics: where additional iteration justifies its cost.
Reusable instructions make routine execution repeatable, giving me more time for consequential decisions.
Why it holds up at scale.
Shared contracts, integrated verification, and deliberate trade-offs guide each wave.
Evidence before acceptance.
Acceptance follows verification of the integrated product against its shared contracts and intended workflows.
Parallelism needs boundaries.
Dependencies, shared contracts, and file ownership determine what can run together.
Improve the delivery system.
Findings improve the instructions, contracts, and checks that guide subsequent work.
Humans own the trade-offs.
Scope, sequencing, spend, and risk stay with me. Agents execute; I decide.
Two products.
Concrete evidence.
Explore the architecture and decisions behind each build.
Formal training.
Applied judgment.
Replit Master Builder
Scrum@Scale Practitioner
PMP
CSP-ScrumMaster
CSP-Product Owner
PSM II
Lean Six Sigma Black BeltThe foundations behind the method.
Thanks to support I got from Michael who was a SVP back then I was able to introduce Continuous Integration, both process and technical solution for all the development teams.
Insightful and patient, methodical approach to problem solving, systems-oriented thinking, strategic-minded leadership, people focused and willing to roll up his sleeves to get things done... Michael is a professional who leads and supports others with incredible effectiveness.
If you are looking for a visionary leader who can help you transition from the ‘abstract’ to the ‘concrete’ swiftly and drive outcomes efficiently - look no further.
Need a leader who can
build with AI?
Let's talk about the product challenge, the team, and the outcomes you need—whether you're improving how your business runs or building something new.