I did this recently. Created a Skill that had access to executing very specific ific (reviewed) script for DB interaction, that connects to your a replica/anonymised DB, read only user, via VPN, via a jumpbox.
I’m working on Userdoc, a spec-driven development workspace.
Break down your software requirements (Userdoc guides you through the process), refine/confirm, setup your technical specs, coding/business guidelines & guardrails, and then create development plans (specs) which can be easily consumed by coding agents via MCP, or by platforms like Lovable / v0 using Markdown.
Working on Cursor background agent integration atm.
Your second point “planning in advance” could be referred to as spec-driven development… it’s a funny term in a sense (didn’t we always do that?), but I think your 7th point drives it home “a very weird form of management” - clear instructions, necessary context, and actionable feedback.
As far as written words go, much more like waterfall than agile.
This is why AI development will be huge in the “Buy vs Build” space… Businesses (with a capable tech team)can build the 20% of the SaaS they need, and stop paying for the 80% every single month.
And then they'll later find out there is a critical group of internal users who was using way more than 20% of the SaaS and roll-out of the replacement application is blocked. Whoops.