Technical design documents in AI workflow process

[Matt-Butler]

Hey there!

First off, thank you for sharing this skills repo and your videos on youtube! I have found them to be very helpful.

I recently watched your video on "Workflow for AI coding" and I had a question about one part of the process.

How do you determine whether the AI is taking the correct technical approach? In my experience, we usually create technical design documents and review them as a team before implementation begins. In the workflow you described, it seems like you move directly from the PRD to creating issues.

At what point would you recommend introducing additional technical context or architectural guidance if the AI starts heading in the wrong direction or produces an incorrect approach?

[AcidRaZor]

I believe this is what he does now with grill-with-docs, but I'm unsure as to what exactly it does (yet) as I play around with different solutions.

It shouldn't be left to the AI to document these, there is (and should always be) a human reviewer.

I believe his examples he has shown in his workflow already has documentation / ADR's before a single line of code has been written.

And you're doing what you should be doing. Technical documentation first with team review and decision making.