Skip to content
Aakash GuptaAakash Gupta

He Uses 7 Claude Code Agents to Build Apps with 0 Employees

Gabor Mayer is a PM at Google who runs a 21-agent Claude Code development team. In this episode, he walks through a live demo building a production mobile app from zero to TestFlight - Confluence for specs, JIRA for tickets, Figma for design, and Claude Code for development. Full Writeup: https://www.news.aakashg.com/p/claude-code-dev-team --- Timestamps: 00:00 AI agents can now run a startup workflow 01:23 Subscribe and AI tools bundle 01:55 Claude Code as your designer, developer, and systems analyst 02:43 Gabor's 21-agent startup team inside Claude Code 04:57 Inside the system analyst agent 05:52 Live demo: zero to TestFlight 08:42 Prompting Claude to define a good system analyst 10:02 Ads 11:53 Building the system analyst workflow 12:17 Why documentation matters: Confluence, Jira, and MCPs 15:30 Why classic PM skills make you a better AI builder 19:15 The scaffolding that prevents AI spaghetti code 22:17 Setting up project-specific agents in Claude Code 26:19 Dictating the full product spec for the hockey rules app 32:19 Ads 35:29 Why dictation changes the quality of AI specs 47:30 Creating the visual direction in Figma Make 55:59 The idea-to-prompt-to-design-to-app workflow 1:06:21 Claude Code starts building the Figma screens 1:23:59 Frontend epics and Figma-linked tickets appear in Jira 1:48:49 The hockey rules AI app is live 1:53:56 Full recap: Claude, Confluence, Figma, Jira, Simulator, TestFlight 2:03:17 Should PMs get AI PM certificates? 2:08:15 How to create a PM portfolio that helps you land top jobs 2:13:32 How to get started building with AI agents --- 🏆 Thanks to our sponsors: 1. Maven: Go from PM to AI builder with Claude Code - https://bit.ly/4bPulv7 2. Amplitude: The market-leader in product analytics - https://amplitude.com/session-replay?utm_campaign=session-replay-launch-2025&utm_source=linkedin&utm_medium=organic-social&utm_content=productgrowthpodcast 3. Testkube: Leading test orchestration platform - http://testkube.io/ 4. Land PM Job: 12-week experience to master getting a PM job - https://www.landpmjob.com/ 5. Product Faculty: Get $550 off their #1 AI PM Certification with code AAKASH550C7 - https://maven.com/product-faculty/ai-product-management-certification?promoCode=AAKASH550C7 --- Key Takeaways: 1. One-prompt vibe coding fails because of context compression - When you give one agent one massive specification, the model silently drops details it considers lower priority. Your color palette, edge cases, and security requirements disappear. Break work into smaller scoped tasks with dedicated agents. 2. The system analyst agent is the most important agent in any AI dev team - It asks clarifying questions one at a time, documents decisions in Confluence, and maps dependencies before code is written. Without it, every agent operates on partial context. 3. Dictation produces 5x more specification detail than typing - Use voice tools like Super Whisper to describe your app requirements. Even imperfect dictation captures more nuance than careful typing. The AI handles the interpretation. 4. Reusable agents encode institutional knowledge - Every painful lesson, API workaround, and MCP quirk gets saved in the agent markdown file. The next project starts from a position of strength rather than from zero. 5. Attach screenshots to every front-end development ticket - Without visual references, coding agents default to generic AI aesthetics. The Figma link or screenshot is what ensures your brand design actually shows up in the code. 6. Build a Spaghetti Agent for code quality - A dedicated code maintainability agent checks naming conventions, circular references, and comment quality after every sprint. It catches structural problems a PM would never spot. 7. The coding phase is the fastest part of building - Specification, documentation, design, ticket creation, and team review take longer than the actual code generation. Do not skip the front-end work. 8. Sprint organization with dependency mapping is essential - Use tags as a workaround for Atlassian MCP limitations. Map dependencies between tickets so agents build features in the right order. Without sprints, agents build on top of code that does not exist yet. --- 👨‍💻 Where to find Gabor Mayer: LinkedIn: https://www.linkedin.com/in/mayergabor/ Maven Course: https://maven.com/gabor/productbuilder X: https://x.com/gabor_pm 👨‍💻 Where to find Aakash: Twitter: https://www.x.com/aakashg0 LinkedIn: https://www.linkedin.com/in/aakashgupta/ Newsletter: https://www.news.aakashg.com #claudecode #aipm --- 🧠 About Product Growth: The world's largest podcast focused solely on product + growth, with over 200K+ listeners. 🔔 Subscribe and turn on notifications to get more videos like this.

Aakash GuptahostGabor Mayerguest
Apr 29, 20262h 15mWatch on YouTube ↗

At a glance

WHAT IT’S REALLY ABOUT

A Google PM builds iOS apps using Claude Code agents

  1. Gabor shows a 21-agent Claude Code setup that mirrors real startup roles (system analyst, CTO, designers, test architect, code maintainability) to produce higher-quality outputs than single-prompt “vibe coding.”
  2. mainstream PM practices—clear specs, dependencies, documentation, tickets, and sprints—become the scaffolding that prevents AI-generated spaghetti code and makes projects maintainable.
  3. He demonstrates an end-to-end workflow: dictate requirements in the Claude consumer app, generate structured Confluence documentation, generate a design system in Figma Make, produce polished screens in Figma via MCP, then auto-create Jira epics/tickets with Figma links/screenshots.
  4. The agents parallelize work (design wiring, backend setup, ticket creation, implementation, review) and then execute sprint-by-sprint to produce a working Flutter + Firebase + vector-RAG app in the iOS Simulator and upload it to TestFlight.
  5. The discussion also covers practical constraints and risks: context overload reduces design fidelity, permissions and secret access must be monitored, API keys must be stored in Firebase Secret Manager, and newer tools like Dispatch/Cowork remain fragile compared to Claude Code.

IDEAS WORTH REMEMBERING

5 ideas

Treat Claude Code like a staffed org chart, not a single assistant.

Gabor assigns specialized agents (system analyst, CTO, test architect, maintainability) so each contributes a focused perspective, similar to a real team reviewing specs, tickets, and code.

The system analyst role is the “keystone” agent for quality.

He uses the system analyst to ask clarifying questions first, break down requirements, document dependencies, and generate Confluence docs and Jira tickets—reducing ambiguity before any coding starts.

Up-front scaffolding beats “one big prompt” for maintainability.

Documentation, tickets, and sprint sequencing act as guardrails that prevent unstructured AI output, reduce rework, and make it easier to extend the codebase later.

Dictation materially improves spec depth and outcomes.

Speaking a long, nuanced prompt is faster than typing and encourages richer constraints (privacy, token budgets, fallbacks), which the agents can operationalize into docs and tasks.

Too much context can degrade fidelity—decompose into tickets to preserve details.

He observes that when agents ingest large context blobs, some details get “compressed” (e.g., design palette not fully used), whereas ticket-based breakdown retains specifics.

WORDS WORTH SAVING

5 quotes

AI agents are writing PRDs, designing in Figma, writing Jira tickets, and even shipping code all from 1:00 PM at 4:00 AM.

— Aakash Gupta

If you build a good specification and you break it down appropriately, then you will have a much better quality end product.

— Gabor Mayer

Vibe coding is just the rebranding of unmaintainable low-quality source code.

— Gabor Mayer

If you have a good specification, then you will have a good product. If you have a shit specification, then you will have a subpar product.

— Gabor Mayer

In two years, the gap will be so big between those who build and those who are just productivity AI users that it will be very hard to catch up.

— Gabor Mayer

21-agent “startup team” inside Claude CodeSystem analyst agent as the workflow nucleusScaffolding vs. vibe coding (avoid spaghetti code)MCP integrations: Atlassian (Jira/Confluence), Figma, Chrome DevToolsDictation-first product specs for richer contextFigma Make → Figma screens → clickable prototype automationTicket-driven development with Figma-linked Jira issuesFlutter + Firebase architecture for an AI mobile appVector embeddings/RAG over official rulebooks + web fallbackCost/usage controls, privacy-by-design, secret managementTool comparisons: Claude Code vs Dispatch/Cowork/Codex/Lovable/BoltPM career strategy: build portfolio artifacts over certificates

High quality AI-generated summary created from speaker-labeled transcript.

Get more out of YouTube videos.

High quality summaries for YouTube videos. Accurate transcripts to search & find moments. Powered by ChatGPT & Claude AI.

Add to Chrome