← All IntelClip / OtherRequirement tracking and adopting Plan Mode as it emerged
From Benchmarking Coding Agents on New vs Legacy Codebases — Denys Linkov, Wisedocs · ≈15:59
“I think we got uh 15 out of 17 requirements right when we were going ahead with the refactor.”
“So, for example, when we started, plan mode was just barely coming into Cloud Code and didn't exist in Cursor, but we adopted it as part of our development life cycle.”
What’s in it
- Shares real numbers from validating a refactor against requirements
- Explains how plan mode got adopted before it existed in Cursor
- Details how their AI engineering guardrails framework evolved over time
Clip transcript
Yeah, so the question was uh when we define certain features and requirements that we go back and check them and make changes uh as well as sort of the guardrails framework. Uh we did. I think we got uh 15 out of 17 requirements right when we were going ahead with the refactor. Um and some of the processes that we added for the actual AI engineering verification, that evolved over time. So, for example, when we started, plan mode was just barely coming into Cloud Code and didn't exist in Cursor, but we adopted it as part of our development life cycle. Yep.
Comments
Checking sign-in…
Loading comments…