[nl]

The kinds of detailed (and excellent) plans Opus or Fable can generate on our large code base would take me maybe 1-2 days to work through and they do in 10-20 minutes.

Maybe I spent 2-4 hours reviewing it, checking things with colleagues etc.

Then I press "go" and maybe an hour later I have a tested system ready for manual review.

It's plans are at least as good as any I've seen. Their weakness is if there are unstated assumptions I have about how things need to be done, so most of my time is now getting those assumptions stated properly and then reviewing.

Why wouldn't I use this? It's the best tool I've used in my 30 years of professional programming.

[DenisM]

Did you manage to setup a discussion with the agent to reveal such assumptions? Sometimes the shave wrong unstated assumptions when contradicted by evidence, but if we’re taking about a plan for the future the evidence is thin.

[nl]

> Did you manage to setup a discussion with the agent to reveal such assumptions?

This is what the plan review is for.

Usually it will have something like "modify abc.ts to update the widget number in the wnx collection" and I'm "hang on - why does that need to be updated when XYZ" and that subsequent discussion will reveal assumptions that are not shared.

[deadbabe]

Cognitive debt

[nl]

Non sequitur