Skip to content

Agent Catalog Overview

FlowForge ships with 53 active specialist agents, each purpose-built for a narrow domain. The Maestro orchestrator never writes code directly. Instead, it consults these specialists, presents options to the developer, and coordinates the specialists chosen to execute the work.

This page introduces the catalog by category. Every agent has a dedicated detail page with its capabilities, typical use cases, and example prompts. See the full table on the catalog index.

All 53 agents are available today as part of the FlowForge core distribution. Some capabilities may move to Pro or Team tiers in future releases (team-wide analytics, managed deployments, advanced auditing), but the agents themselves — the specialist prompts that power FlowForge’s orchestration — are and will remain free to use.

The phase-0 specialist dispatched first on any legacy, existing, or unfamiliar codebase. It reads cheaply on the Sonnet model tier so expensive specialist tokens are spent only on verified knowledge.

  • fft-code-explorer — Sonnet-class ingest: source tree scan, lockfile version extraction, schema inference from migrations (no live creds), framework detection, and structured specialist-wave dispatch. Produces a laudo + ERD + FF-branded diagrams + a filled project CLAUDE.md. ForgePlay #1 entry point.

These agents shape the what and the why before any code is written.

  • fft-requirements-analyst — anti-fabrication requirements interrogation, outside-in interrogation, 8-artifact handoff packet. Dispatch before fft-architecture on greenfield work.
  • fft-architecture — system design, ADRs, SOLID principles, microservices and monolith trade-offs.
  • fft-project-manager — task breakdown, sprint planning, milestone tracking, GitHub structure.
  • fft-product-owner — requirements, user stories, backlog prioritization, stakeholder alignment.

Server-side craft, from contract design to persistence.

  • fft-api-designer — REST, GraphQL, gRPC, WebSocket; OpenAPI specifications; versioning and contract testing.
  • fft-backend — Node.js, Python, Ruby, Java, Go; scalable server architectures with 80%+ test coverage.
  • fft-database-architect — the data-model head: store, ERD, access matrix and migration plan, designed on files; never opens a connection.
  • fft-dba — the only agent that touches a live database: rehearses, reads, applies under a founder grant, and reports.

Everything the user sees and touches — led by the design authority that briefs every surface.

  • fft-design-architect — master design authority: holds the guideline corpus (Apple HIG, Material 3, WCAG 2.x, FlowForge design canon) and emits the per-work design brief every leaf implements. Dispatch first on design-strategy and multi-surface work.
  • fft-frontend — React, Vue, Angular; component architecture, accessibility, performance.
  • fft-designer — web + print/editorial (papelaria) UI/UX: the Manual, PDF-from-HTML, reports, and stationery as well as web surfaces; design systems, type-scale systems, page grids, print stylesheets.
  • fft-web-designer — dedicated web visual-design leaf: the look of the marketing site, admin dashboard, and desktop web-chrome — composition, hierarchy, responsive visuals, motion, theming.
  • fft-brand-architect — brand identity, color theory, typography, design tokens, guidelines.

Platform-native and cross-platform — three specialists, one per platform.

  • fft-ios — Swift, SwiftUI, UIKit, structured concurrency.
  • fft-android — Kotlin, Jetpack Compose, Hilt, Room.
  • fft-flutter — Dart 3+, Riverpod 2, GoRouter, cross-platform targets.

The only dedicated TUI design-and-craft hierarchy in the public LLM-coding ecosystem — architect decides composition, designer crafts each screen, implementer writes View/Update code.

  • fft-tui-architect — strategic composition, Charm-ecosystem adoption, layout budget, focus model, and the visual full-screen QA gate. Dispatch first for composition questions.
  • fft-tui-designer — per-screen visual design: the mockup, visual hierarchy, color/glyph/label co-render, spacing-token application, state tables, and the “gorgeous” bar. Hands fft-tui an implementation-ready screen spec.
  • fft-tui — Charm.sh BubbleTea, Elm MVU, lipgloss, 60 fps render budgets, CVD-safe accessibility.

The gatekeepers of production readiness.

  • fft-qa — quality assurance strategy, test automation, and regression gates.
  • fft-code-reviewer — standards enforcement, pattern analysis, architectural validation.
  • fft-security — threat modeling, OWASP compliance, defense-in-depth.
  • fft-web-quality — Playwright 4-viewport screenshots, Lighthouse CWV, axe-core WCAG AA, broken-link detection.

Ship it, run it, observe it.

  • fft-devops-agent — CI/CD, Docker, Kubernetes, Terraform, monitoring, cost optimization.
  • fft-github — git workflow, PR automation, issue management, release operations.
  • fft-release-engineer — the release operator: pre-flight, notes and letter pack, the cut up to its consent request, tag, staging, verify by name, rehearsal, install parity.
  • fft-documentation — technical writing, API docs, architecture docs, user guides.
  • fft-documenter-br — Brazilian Portuguese documentation with correct diacritics.
  • fft-documenter-es — Spanish documentation: RAE orthography, tildes, inverted punctuation, Latin-American register.
  • fft-marketing-architect — the marketing head: the positioning canon and locked message spine, launch tiers, the calendar, lane routing and the split between lanes.
  • fft-content-strategist — landing-page copy, SEO, email, conversion optimization.
  • fft-social-media — multi-platform social content, calendars, engagement analytics.
  • fft-devrel — developer relations: Hacker News, Reddit, Product Hunt, Discord, creators and technical stories — drafts, never posts.
  • fft-product-marketer — the claims table, battlecards, sales enablement, case studies and release-announcement packaging.
  • fft-lifecycle-marketer — the newsletter and e-mail programme: each issue assembled, the list’s health, the send-day checklist — drafts, never sends.

Hierarchical: fft-cs-architect designs the strategy; fft-cs-analyst executes it against accounts.

  • fft-cs-architect — CS strategy: onboarding/adoption/retention/expansion architecture, health scoring, churn-risk, QBRs, playbooks.
  • fft-cs-analyst — executes the play brief: playbooks, health reports, touchpoint cadence, renewal runway, outcome reports.

Hierarchical: fft-paid-media-architect designs the campaign; fft-media-buyer operates the consoles.

  • fft-paid-media-architect — paid-media strategy: audience research, positioning, offer, funnel, Meta + Google/YouTube channel mix, budgets, measurement plan.
  • fft-media-buyer — console operations: pixel/CAPI + conversion setup, audiences, campaign build, budget entry, pre-launch QA, optimisation loop.

Hierarchical: fft-analytics-architect decides how truth is measured; fft-data-analyst executes that brief against real data; fft-dataviz-designer decides which chart form tells which truth.

  • fft-analytics-architect — measurement strategy: metric and indicator design, study design, threshold derivation, method selection, back-test discipline.
  • fft-data-analyst — executes the measurement brief: sourced pulls with timestamps, rule projection over real rows, cohorts and deltas, evidence reports.
  • fft-dataviz-designer — indicator-to-chart-form mapping per the perception canon, dashboard composition, CVD-safe encoding, chart specs.

Hierarchical: fft-legal-architect gathers the facts, decides jurisdiction and instruments, and writes the legal brief; fft-legal-br and fft-legal-us draft and analyse against it. Not legal advice — counsel licensed in the jurisdiction reviews before anything is signed or filed.

  • fft-legal-architect — legal strategy: fact inventory, jurisdiction and instrument selection, graded issue list, cross-border reconciliation.
  • fft-legal-br — Brazil: drafts and analyses in pt-BR under LGPD, Marco Civil, CDC, Lei do Software, and INPI filings.
  • fft-legal-us — United States: drafts and analyses in English under state contract law, CCPA/CPRA, and USPTO/Copyright Office/DMCA filings.

Hierarchical: start with fft-ml-architect for strategy, then route to a specialist.

  • fft-ml-architect — strategic advisor: model selection, RAG vs fine-tuning, GPU allocation.
  • fft-llm-openweight — local LLM deployment: vLLM, Ollama, quantization, Qwen/Llama/DeepSeek.
  • fft-rag-engineer — retrieval architecture, pgvector, embeddings, chunking, reranking.
  • fft-agent-frameworks — CrewAI, LlamaIndex, LangChain, custom multi-agent orchestration.
  • fft-performance — profiling, caching, load testing, scaling strategies.
  • fft-medical — Brazilian healthcare compliance (ANS, TISS, TUSS, CBHPM, LGPD).
  • fft-agent-creator — creates and validates new FlowForge agents from specifications.

For the complete side-by-side list, see the catalog index. To understand how the Maestro selects and coordinates these agents, read Core Concepts: Maestro Pattern.