Some lessons from my latest build: a personal assistant for my daughter Luna, 17. She studies at Sora Schools, an online school, and asked for an assistant that organizes school and life with her: a morning panel, weekly plans that roll up into the trimester, and one hard rule: it never answers schoolwork. Her school's AI policy went into the workspace verbatim, as a rule the assistant has to follow.
Speed comes from the process, not from rushing. In the morning I recorded a discovery interview with her. In the same day the factory ran the whole pipeline: spec interview, value baseline (the "before", measured in her own words), workspace design, deploy and delivery. By 3pm she had cloned the repo and was using it on her own machine. None of the phases was skipped. The process is what made one day possible.
The checks that catch things are the ones you don't run yourself. Three cold reviews, each by an agent with no memory of the build. A cold audit of the design against my own decision principles caught one factual error and proposed four improvements, all applied before I approved it. A cold walk test dropped a fresh agent into the finished workspace with one task: orient yourself from the files alone. It found the right place after reading just two files, and flagged two references to files that don't exist yet. And between every phase there was a human gate: nothing moved without my explicit approval.
Delivery is a repo, not a meeting. The product is fi the workspace as a private GitHub repo, I added Lunaas a collaborator, and a one-page SETUP guide sits in the repo itself. She cloned it with GitHub Desktop, opened the folder in Claude Code, and started. That was the whole handoff
In two weeks I'll be back here with results. We measbout 30 minutes a day spent planning, plus the worstpart of all: carrying everything in her head all day. So we'll know exactly what changed. Measure the before, so you can show the after!