← All IntelClip / Developer ToolsYou are the accountable code reviewer, not the agent
From Using Spec-Driven Development for Production Workflows - Erik Hanchett, AWS · ≈5:27
Establishes the trust boundary for spec-driven workflows: humans must review every generated requirements doc, design doc, and diff because accountability never transfers to the agent.
What’s in it
- Establishes the trust boundary for spec-driven workflows: humans must review every generated requirements doc, design doc, and diff because accountability never transfers to the agent.
Clip transcript
And just be careful about giving too much trust. Uh remember everything in the spec-driven development flow is you, meaning that you are the human in the loop, so to speak. You need to be the code reviewer of all the code that's generated through this process. You need to be interactively looking at the design documents and the requirements documents that are created because at the end of the day, if something goes wrong, you are the person that are going to be blamed for it, not the agent. And uh that's not to say that we don't use tools to help do code reviews. Someone once told me like, are you saying you're the human in the loop, you do the code review, no one else? Of course, we might have multiple be doing people doing code reviews and definitely use your normal AI coding assistants and and review tools to help you review any pull request that you
Comments
Sign in to comment.
Loading comments…