A Workflow i've been using quite successfully for a few days

So I’ve been using o3 and sonnet together, switching between the two. Ive found Sonnet better at documentation and o3 better at generating accurate code.

Step one is to get o3 to write a development plan, then have Sonnet apply it to a living HTML document:

Then get O3 to read the document and apply code changes, stepping back to Sonnet if it seems to go squirly.

There is huge benefit in having things like my db path, tables, function names and parameters all pre-defined so the LLM’s can reference them during the development process. It also gives me one single place where I can remind myself what on earth I was trying to do.

i tend to work in chunks, so Ill finish off the first bit of the program, based on the doc, the update the doc with any missing bits or changes. Its like a proper spec which is developed alongside the software.

Seems to be going well so far.

2 Likes

how are you making o3-mini do all that?

for me:
-it loses context quickly
-only writes 8 lines of code at max
-doesn’t apply changes often

I didnt do anything special, just enabled it and started using it, its a little quirky sometimes at the moment in that it’ll say its done an update but hasnt, but I think what its really saying is “shall I do this…” because when i encourage it to actually do it, it seems to go ahead. I did update cursor to 0.45.9 so that might be important.

I am on 0.45.9 too, and the missing applying is actually a bug already brought up on forums.

are you using composer or chat?

That’s similar in nature to what I’ve been doing. I’ll give r1 the section of code i’m working on. tell it the feature i want to implement. tell it to ask me 5 clarifying questions. respond and ask it to ask for 3 clarifying questions. ask for a final clarifying question. switch to 03, and simply state, ‘please begin the implementation’. The context window is now prefilled with everything o3 needs