[harikshore]

Answering your questions from my knowledge level on AI:

Managing AI agents is like running a knowledge business. If you are not an expert enough to understand what agents are doing, there is still large room for errors. Its important to set design decisions early in the development process.

Your questions:

3. I think this is absurd. Agent can generate the test cases, but you still have to verify the tests are actually valid.

4. The architecture document should be the source of truth. SO when a engineer reviews they know what to look for & flag/fix. The comprehensive the document is the better. Version it based on what the prototype carries. — Data models, API design, Services, Roles, etc. You can ask this to AI — What all should a high/low level SDD carry?

5. Just make sure the architecture doc is solid, development is as per the document, ask AI to generate/perform regression test cases and document them as well (pass/fail).

So the engineer knows where things exactly stand.

Thats the best can do

Appreciate thoughts on this.

[thegreatkahuna]

I agree that in perfect world I could have done this exercise with competent engineers and a UX desginer. I know about software development processes and applied that to e.g. testing and hardening, but it is not a substitute for deep technical knowledge. THe idea behind having a separate agent create the tests is to that then the coding agent couldn't get functionality to work or fix bugs by weakening the test. I believe Bob Martin has talked about this. Noted about the architecture document - will have to ensure it is as solid as possible. I already run the full CI pipeline that we run for our app + the new ones that the agents developed - would it be good to have additional regression tests?