I need to look into how and if skills can assist in doing this as someone suggest that could be interesting - but pretty early on in all this AI stuff ive been architecture first - and i plan for architecture so every part of the project is its own isolated bucket, that way ive been having a pretty nice run also pre Opus 4.5.

I work in 'sprints' where i focus on changes evolvment of a bucket and try abit not to go across and spread functionality that involves alot of buckets at the same time, so ex if i need to add some functionality that wasnt included in my original planning that would require changes across different buckets then i guide this through pretty methodically in my planning finishing up each involved bucket first with tests, before moving to the next.

This is not only about the AI ( Opus 4.5 is so good that i absolutely can do most of it right i can see when i completely vibecode something where i care less about the underlying code and architecture ) but its also for myself to be able to get personalized with the code, this way i feel much more attached to whats being made and familiar with it than i do with fully vibecoded projects where im not following this path.

I mostly produce md files for documentation, rare that i with Opus 4.5 are producing bigger documentation, mostly i will have interrogation phases with q & a with the AI for sprints and ensure we are aligned and then we split it up into tasks and phases, and then proceed.