IMHO, you still need to be a developer to be able to use AI effectively. If you start with a really solid schema, or an existing framework, AI is great at building on top of that. If you give it specific guidance for what and how you want it to develop code, it can do a good job. It is NOT just "lol write me a network utility lol" -- that is a path to disaster.
I've also had good luck with updating and modernizing older code, migrating to a new frameework, and refactoring.
If i'm using claude code, my steps go something like this.
1. Using plan mode, analyze the code base, create a thorough plan and testing strategy for XYZ (Or I provide SQL schema, or I provide a thorough plan of what I want to do, etc.)
2. Refine Claude plan mlutiple times until I'm happy with it
3. Start with writing a set of unit tests to confirm current behavior
4. Implement the first part of the project (this is not coding the whole thing in one shot)
5. Run unit tests, check for regressions.\
6. Rinse and repeat..
Steps 1 and 2 -- with no code being written -- are probably the most important parts.
I should also add that, imo, this will be a relatively short moment in time. I've seen people who are spinning up dozens of agents at the same time -- backend designer, frontend designer, security consultant, css specialist, etc -- that all work together and iterate amongst themselves.
We've been running a beta test of some new software, and one beta tester out of ~30 people hit an error. We could not reproduce it. Claude took ~5 hours, but using Claude to remote control Chrome, in conjunction with analyzing the state of the backend database, and auditing the codebase, Claude was able to reproduce the error and suggest a fix. In this case, we disagreed with the fix (rather, we went for a bigger logical change as opposed to a bandaid), but we've had really great luck with using Claude Chrome mcp as a beta tester.