# Code done in week 9. Shipped in week 14.

> Not one of those five weeks was code.

- **Format:** short video, 9 steps, ~51 seconds
- **Topic:** Why one AI coding agent is not a team — a Flutter and Firebase app is code-complete in week nine and ships in week fourteen because security rules, licences, changelog, crash reporting, analytics and accessibility have no owner, and how role agents plus hook checks catch each job the week it appears.
- **Author:** Suthahar Jegatheesan (MSDEVBUILD)
- **Category:** AI · AI
- **Published:** 2026-07-17
- **Tags:** aiagents, githubcopilot, flutter, firebase, devops, aicoding, softwareengineering, msdevbuild
- **Canonical URL:** https://blog.msdevbuild.com/shorts/ai-agent-team-one-agent-not-a-team/

---
## What you'll learn

- Why a fast coding agent moves the bottleneck
- When a job should be a hook instead of an agent
- Which four agents to build first

## Understand it one step at a time

### 1. Code-complete, week 9

One coding agent, a green build and every test passing.

### 2. Week 10: the rules

Firestore rules from week two: any signed-in user reads any order.

### 3. Week 11: one licence

A package the store build cannot ship, spread into three features.

### 4. Weeks 12 to 14

No changelog, swallowed errors, analytics in 2 of 11 screens, unlabelled buttons.

### 5. Agent or hook?

If a script can answer it yes or no, it is a hook. Judgement is an agent.

### 6. 14 hook checks

pre-commit: 10 checks. pre-push: 4. Each one a script.

### 7. Four agents first

Solution architect, code review, testing, security. In that order.

### 8. The next release

The bad licence fails the push the day it is added. Code-complete week 9, shipped week 10.

### 9. One agent is a developer, not a team

Agents for judgement. Hooks for rules. Start with four.

---

## The takeaway

**One agent is a developer. Not a team.**

Give every job around the code an owner: an agent for judgement, a hook for rules.