Software is over: when code stops being scarce, what becomes scarce instead?
In October 2026, an open-source project picked up 20,000 GitHub stars in a single day. The same month, one developer cloned seven Adobe apps with AI.…
WatchYouTube channel · 21 October 2026 · 14:54 min
A regulated application costs what it costs because of the seats, not the typing: seven stages, each a handover, documentation written last from memory, and an audit that has to reconstruct who verified, who decided and what the evidence was.
This tutorial shows how to give every seat to an agent and keep a person at every gate. Ten Claude Code agents, three skills and one workflow script specify, build, test, verify, document and release a small Symfony API from a requirements document, then maintain it from its logs and its request inbox. The orchestrator never writes code. The tester never reads the diff. The verifier starts fresh. The tag, the merge and the push stay yours.
Four chapters: the typical workflow of a regulated application (three flows, seven stages), the TicketFlow demo (build, maintenance and release flows on one-screen diagrams), the fundamental concepts (what a skill, an agent and a workflow are in Claude Code), and how to build your own skills and agents from your own process.
What a fresh session did on the demo with nothing but /improve, on 2026-10-15: two rounds, three bugs fixed, two feature requests shipped, eight decisions asked and answered, every item passed on its first verification; round one took 27 minutes, round two 9, the release 10. The numbers are in the tutorial repository.
The demo repository (public, clone it and run the three flows)
Powered by https://www.shenyi.dev
More videos
In October 2026, an open-source project picked up 20,000 GitHub stars in a single day. The same month, one developer cloned seven Adobe apps with AI.…
Watch