Aakash GuptaHe Uses 7 Claude Code Agents to Build Apps with 0 Employees
CHAPTERS
- 0:00 – 2:43
AI agents running a full startup workflow in hours
Aakash frames the episode around a new reality: agents can now handle core startup tasks—PRDs, design, ticketing, coding, and shipping—end to end. Gabor introduces the promise: going from zero to an iOS TestFlight build in a single session using an agent “team.”
- 2:43 – 4:57
The 21-agent “company” inside Claude Code (roles and responsibilities)
Gabor explains how he models Claude Code agents as a real cross-functional org, expanding from 15 to 21 specialized roles. The system analyst is the central node, but he also uses agents for CTO/architecture, brand, design, testing, performance, privacy/data governance, and maintainability.
- 4:57 – 8:42
Under the hood: the System Analyst agent definition and why it’s the linchpin
They open an agent markdown definition to show how the system analyst breaks down requirements, flags ambiguity, asks clarifying questions, and tracks dependencies. Gabor emphasizes that high-quality documentation and ticketing originate here, improving downstream build quality.
- 8:42 – 11:53
Kickoff from the consumer Claude app: voice-first ideation and role prompting
Instead of starting in a terminal, Gabor begins in the Claude consumer app to make the workflow accessible and voice-friendly. He demonstrates prompting Claude to behave like a “good system analyst” and sets the app idea: an AI hockey rules assistant.
- 11:53 – 12:17
Defining a “good system analyst” and the clarifying-questions-first workflow
Gabor shows how he first asks Claude to define the system analyst role (good vs bad), then uses that to set expectations. He instructs the agent to ask questions one at a time and not to write docs until understanding is complete—preventing premature output and messy direction changes.
- 12:17 – 22:17
Documentation + ticketing backbone: Confluence/Jira via MCP and why PM skills still matter
Gabor connects Atlassian tools via MCP so Claude can write Confluence docs and create Jira issues directly. He argues classic PM skills (requirements, decomposition, documentation) are even more valuable with agents because they prevent unmaintainable “AI spaghetti code.”
- 22:17 – 26:19
Project setup in Claude Code: agents, permissions, and guardrails
Gabor switches to Claude Code, differentiating “acting like an agent” in chat vs real project agents in Claude Code. A live hiccup forces him to recreate the project folder and re-run setup, highlighting practical guardrails: watch permissions, keep work inside the project directory, and avoid risky access requests.
- 26:19 – 47:30
Dictating the full product spec: stack, RAG sources, limits, privacy, and secrets
Gabor dictates a detailed spec for “Rule Ask”: Flutter iOS app, Firebase backend, IIHF rulebook + situation book as RAG sources with vector embeddings, and a friendly referee persona. He adds cost controls (20k-word limit with 24h cooldown), privacy constraints (no server-side user storage), and strict API key handling via Firebase Secret Manager.
- 47:30 – 1:06:21
Visual direction in Figma Make: brand kit, typography, and palette from inspiration
Gabor uses Figma Make to generate a comprehensive design system (typography, colors, buttons, states) using inspiration screenshots. He notes an important prompt constraint—ask for “inspiration, not copying”—to avoid tool refusal and keep the workflow moving.
- 1:06:21 – 1:23:59
Claude Code drives Figma: generating screens and a clickable prototype with a UX agent
With MCPs connected (Figma, Chrome DevTools), Claude Code creates the actual Figma screens from the spec and style guide, then adds prototype links (“arrows”) automatically. They observe that agent-driven Figma manipulation produces usable UI quickly and avoids generic ‘AI-looking’ defaults when design context is correctly anchored.
- 1:23:59 – 1:48:49
From design to execution: Jira epics/tickets with Figma links, sprints-by-tags, and parallel work
The system analyst and other agents generate Jira epics and detailed tickets, ensuring every frontend ticket includes a screenshot or Figma link so developers don’t drift into generic UI. Backend setup tickets are created first (Firebase basics, domain, secrets), then frontend and backend workstreams parallelize; sprints are approximated using tags due to MCP limitations.
- 1:48:49 – 2:13:32
Shipping the hockey rules app: simulator demo, RAG transparency, and TestFlight upload
After sprint execution, the app runs in the iOS Simulator with a working RAG pipeline and an “observer mode” showing retrieval hits, token usage, and latency. They upload the first build to TestFlight, discuss Apple processing/review timelines, and recap the full pipeline from dictation to deployment.
- 2:13:32
Career layer: AI PM certificates vs building, portfolios that prove capability, and getting started
The conversation shifts to careers: Gabor argues certificates matter less than hands-on skill and proof of building. He recommends creating portfolio apps with demonstrable “stories” (debugging retrieval, tuning scoring/thresholds) and advises newcomers to start by asking questions in their preferred LLM, then accelerate with structured programs if needed.
Auto-generating Confluence documentation from the clarified spec
After questions are resolved, Claude writes structured Confluence pages (product overview, architecture, agent specs) via MCP. Gabor checks the docs primarily for fidelity—whether the generated artifacts accurately reflect the spoken requirements and technical approach.
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