← All IntelClip / OtherDistinguishing this approach from plan mode and spec-driven dev
From Velocity Sickness: What Happens When Your Whole Team Gets 10x Faster — Matt Dailey, Ref. · ≈12:18
“The way I like to conceptualize this is as the portal to the software system, where you are like Tony Stark and you're like, "Show me what matters."”
“What you want is to separate the the agent as the action and the doc as the state.”
“You're ultimately doing context engineering in this doc, so that every agent is largely stateless and starts from this place um the same place.”
What’s in it
- Pitches a shared, durable 'doc' as state separate from AI agent actions
- Reframes AI agents as a 'portal' for surfacing relevant system context
- Explains why stateless agents built on shared docs beat ephemeral chat sessions
Clip transcript
spectrum and development. That's a great tool, too. I'm talking about something in the middle. Plan mode is great, but it's largely a a rich chat message where the agent is saying, "Hey, here's a like better visualization of what I'm trying to express to you." Yeah, that's great. But it's still in this isolated ephemeral environment. And what I'm suggesting is something more more durable, more shared, more long-lived that you and your team are spending time on. Similarly, the spectrum and development where we just define the behaviors, we operate at the like product level, is a little far away from the engineering reality. The engineering reality is that I need to understand my system and have a tool that like helps me understand that system and lay out those key decisions in a in a technical sense. The way I like to conceptualize this is as the portal to the software system, where you are like Tony Stark and you're like, "Show me what matters." And you're like, "I'm working on this. Pull out the bits that are relevant." And AI is amazing at finding things that are related to other things, helping you find what's what's relevant and lay them out on the table in front of you. Organize the pieces in the way you want to represent how you want the system to grow. But the big conceptual flip here is actually that we're pulling out the state. So, when you're living and working in a a long-lived session with an agent, there's this implicit context being built up like over that work, and that's great. Um But there's you're also doing actions and it's it's not shared. What you want is to separate the the agent as the action and the doc as the state. And so, you can spawn new agents that have the same context or starting from the same place that are able to collaborate and work on the same same piece of context and state. You're ultimately doing context engineering in this doc, so that every agent is largely stateless and starts from this place um the same place. And what that gives you is your team and yourself can look into this and understand what actually is in here. What are the decisions that are being made um and have a a clear understanding of what the key decisions are.
Comments
Checking sign-in…
Loading comments…