Seven Agents Before a Line of Code: The Week 0 Agentic Planning Pipeline

Before writing a single line of contract code, I had seven agent specifications. Each one had a defined scope, a list of inputs it consumes, specific outputs it produces, and an explicit list of things it does not do. That last part matters. An agent with clear boundaries is more useful than one that tries to cover everything. This is what Week 0 actually was: not "I planned the project," but a structured pipeline of specialist AI agents — each given a specific brief and a bounded scope — coordinated by me as the Orchestrator. Most run on Claude. One deliberately doesn't. The pipeline produced concrete artefacts. Those artefacts feed the next agent. Nothing advances until the handoff is ready. The agents are specialists, not generalists The pipeline that runs every week of the build is: Research → Dev → Security → Deploy → QA → Copywriter → Distribution . Those are hard sequential dependencies. Before Week 1, I needed to establish the infrastructure every agent in that chain would rely