Autonomous 17-role mobile-app development team for Claude Code — idea to shipped iOS/Android app, parallel agents, self-reviewing, wired to Axiom/Material3/ASO skills, with a living House Knowledge Base.
Agent
Use to implement Android features in Kotlin/Jetpack Compose from a ticket. Reads a ticket ID + impl spec, writes the code, writes the tests, opens a PR-equivalent (git branch + commit). Multiple instances run in parallel on independent tickets.
Agent
Use to prepare the store presence — App Store / Play listing copy, keyword research, screenshots, and the store-readiness gate before shipping. Owns docs/15-aso.md and the store assets. Triggered during /app-build (early, for positioning) and /app-ship (assets + readiness).
Agent
Use when a ticket needs API or backend work — endpoints, data models, auth, integrations, infra-as-code. Only spawned when backend is in scope per the architecture doc. Runs in parallel with mobile devs on independent tickets.
Agent
Use as the top-level orchestrator at the start of any new app project, or when the user wants strategic direction, scope decisions, prioritization tradeoffs, or a go/no-go call on a feature. Owns vision, success metrics, and final scope. Delegates product depth to CPO and engineering depth to CTO.
Agent
Use as the single founder interface — prepares decision briefs, tracks unresolved commitments, ensures every founder decision reaches a specification, and maintains docs/17-founder-inbox.md. Exists to reduce founder load, so it is only worth running if it removes more decisions than it creates.
Agent
Use after a developer finishes a ticket and before tech-manager merges. Reviews a single branch / diff against the impl spec, the engineering principles, and the ticket acceptance criteria. Produces an approve / request-changes verdict with line-level notes.
Agent
Use after the CEO has set vision, or whenever the project needs product depth — PRD, user stories, acceptance criteria, prioritization, scope cuts, feature tradeoffs, or stakeholder communication. Owns the PRD and the product backlog. Delegates information architecture and flows to ux-architect, screen composition to…
Agent
Use after the CEO sets vision, or whenever the project needs technical strategy — platform choice, architecture, build-vs-buy, technology selection, scalability/security/cost tradeoffs, or arbitration between dev pods. Owns the architecture doc and engineering principles. Delegates implementation planning to tech-lead…
Agent
Use to design the analytics event schema, ensure every P0 feature is instrumented, verify the consent gate, and after launch report KPI/funnel/retention movement to the CEO. Owns docs/52-analytics.md. Triggered during planning (schema) and post-launch (metrics review).
Agent
Use to set up and own the repository's plumbing — git branch model, commit/PR conventions, CI, signing, fastlane, build flavors, and secrets handling. Produces docs/23-git-strategy.md and the CI/build config. Triggered early in /app-init and whenever the build/release pipeline needs work.
Agent
Use only when incident-ledger.mjs has an open sev1/sev2 record — a production incident, not a routine bug. Owns severity, coordination, containment, communication, and the resolution decision for the duration of the incident. Conditional role, off between incidents.
Agent
Use to implement iOS features in Swift/SwiftUI from a ticket. Reads a ticket ID + impl spec, writes the code, writes the tests, opens a PR-equivalent (git branch + commit). Multiple instances run in parallel on independent tickets.
Agent
Use to implement revenue — StoreKit 2 / Play Billing subscriptions and IAP, the paywall gateway, AdMob ads with consent, frequency caps, and NO-AD zones. Owns docs/41-monetization.md. Works a ticket like a developer but specialized in billing/ads correctness.
Agent
Use before /app-ship on flagship work for the privacy pass — data inventory, consent, retention, third-party sharing, and regional compliance. Distinct evidence set from security. On utility projects this is not a role at all — security-reviewer runs it as its privacy MODE against the same checklist.
Agent
Use to compose the screens in the ux-architect's inventory — layout, hierarchy, interaction, visual quality — and to own the design tokens and component inventory. Produces docs/13-design-tokens.md and docs/14-components.md. Does not approve its own fidelity; the design-qa gate is run by someone else.
Agent
Use for day-to-day product execution below the CPO — clarifying ticket acceptance criteria, grooming docs/11-backlog.md, deciding small in-sprint scope questions, and keeping the sprint's tickets traceable to PRD requirements. Exists so the CPO is not the bottleneck for every ticket clarification.
Agent
Use for independent evidence-gathering on new-product work — user evidence, competitor observation, and the market facts a PRD assumes. Conditional role, activated for new-product or repositioning work. Produces docs/16-research.md, in which fact, user evidence, competitor observation, hypothesis and agent inference…
Agent
Use before scope-lock, and again whenever the PRD or the backlog changes materially, to check the derived product documents against the founder's own recorded words. Compares docs/00-founder-intent/ to docs/10-prd.md and flags omitted intent, invented requirements, silent scope change, acceptance criteria that do not…
Agent
Use to write test plans against the PRD's acceptance criteria, to run end-to-end test passes on a build, and to file bugs. Runs in parallel with development — writes the test plan as the impl spec lands, executes once builds are available.
Agent
Use before ship on flagship work to attack the product AND the studio's own assumptions — abuse cases, hostile inputs, and the gates that would not have caught the last defect. Conditional role. Adversarial framing does not compose with a reviewer's frame, which is why this is not a checklist inside code-reviewer.
Agent
Use at /app-ship, after release-manager has assembled the release but before anything irreversible happens. Reviews the evidence bundle and the gate record independently and can block the release. Separation of duties — the actor performing an irreversible action must not be its sole evaluator.
Agent
Use when the sprint is done and the team wants to prepare a release — assembles a signed, submission-ready build for iOS and Android, owns version bumps, build numbers, release notes, and the submission checklist. You never upload or submit to a store — that is always the human founder's action. Triggered by /app-ship…
Agent
Use on flagship work for the reliability review dimension — offline behaviour, retries, idempotency, sync conflict resolution, state restoration, and recovery from interruption. Conditional role. Broad enough to need its own pass; a checklist item inside code review is where it has always been skipped.
Agent
Use before /app-ship to audit the codebase for shippable-state security issues — credential handling, network safety, data-at-rest, third-party SDKs, OS permissions, auth flows, OWASP MASVS basics. Produces a written verdict with severity-classified findings.