Skip to content
FlowForge
ForgePlay

Describe the goal.
FlowForge runs the play.

A ForgePlay is a pre-built team of specialist agents that takes you from near-nothing to a shipped outcome — in a single command. You describe what you want; the play coordinates the specialists, end-to-end, with zero context switching.

Watch the play run.

Every play runs as a live swim-lane: you see which specialist is working, what it is producing, and how the pieces converge — in real time. In the terminal today; on the dashboard soon.

The play library

Each card says where its play stands — shipping now, in design, or on the roadmap. Nothing here is a mockup: a shipping play is a real, repeatable agent chain you can run today.

Understand what you already have Shipping now

Point FlowForge at a project you already have.

Install FlowForge on an existing — or legacy — codebase and it reads the whole thing: source tree, database schema, dependencies, exact framework versions. Then it hands back a laudo and a set of artifacts you can act on the same day.

  1. Code Explorer

    Reads the full source tree, DB schema, and lockfiles to detect framework, exact versions, languages, and architecture.

  2. Database

    Reconstructs the ERD and schema map straight from your migrations — no live credentials required.

  3. Architecture

    Writes the architecture laudo: how the system actually fits together, where the seams are.

  4. Domain Specialists

    Backend, frontend, or mobile experts engage automatically — exactly the ones your stack demands.

You get back a project laudo, an ERD, themed architecture diagrams, and a filled-in CLAUDE.md — the context file that makes every future session sharper.

From a name to a live page Shipping now

Give it a product name and a vision. Get a live landing page.

Describe your product in plain language. Six specialists run the entire brand-to-page pipeline in one coordinated session — no brief, no back-and-forth, no waiting on hand-offs.

  1. Brand Architect

    Creates your logo, selects a palette, and generates the design tokens that define the brand.

  2. Content Strategist

    Writes headlines, feature copy, and SEO-ready page text aligned to your audience.

  3. Designer

    Designs the layouts and component specs — pixel-precise and accessibility-compliant.

  4. Frontend Engineer

    Builds the real page. Responsive. Production-grade Astro.

  5. Quality & Performance

    Validates accessibility, Core Web Vitals, and cross-browser rendering.

  6. Code Reviewer

    Final quality gate before merge. Zero shortcuts.

One play. Six specialists. Zero context switching. → a production-ready landing page plus a complete manual da marca (brand manual).

From a plain-language idea to written tickets Shipping now

Describe the feature in plain words. Get a plan, then the tickets.

Anyone on the team can describe what they need in their own language and walk away with the documentation discipline a senior team would have produced: requirements, an architecture decision, a design spec, a PRD — and, once you ratify the plan, the micro-tickets written from it.

  1. Requirements Analyst

    Grills the brief until it is answerable — scope, acceptance criteria, the questions nobody asked.

  2. Architecture

    Writes the ADR and the ERD chart: what gets built, in what shape, and why that shape.

  3. Designer

    Produces the screen and UX spec plus the blueprints the tickets will cite.

  4. Product Owner

    Assembles the PRD and the PO brief into one plan — the single thing you ratify.

  5. Product Owner

    Writes the micro-tickets from the ratified plan. Never before it: no ratification, no tickets.

  6. Project Manager

    Nests the tickets in a milestone your dev team can start on Monday.

A ratified plan and the micro-tickets derived from it, each one attached to a milestone — with the requirements, ADR, design spec and PRD behind them, not lost in a thread.

From what you sell to the campaign that sells it Shipping now

Describe what you are selling. Get the campaign — and every script it needs.

A chain of specialists researches the market, sets the offer and the funnel, and lays the campaign out across Meta and YouTube — then bundles it into one plan you approve. Only after you say yes does it write the creative. No budget is spent anywhere in the play.

  1. Requirements Analyst

    Grills the brief: the product facts, the audience, the budget envelope, the constraints.

  2. Product Owner

    Frames the value — who the customer is, which offer leads, what counts as a win.

  3. Paid Media Architect

    Research, positioning, funnel, channel mix, budget and the measurement plan — the one plan you ratify.

  4. Design Architect

    One campaign brief plus a per-asset delta, each carrying the guidelines and the claims table.

  5. Creative Leads

    The specs: long-form video with the full roteiro, Reels, Shorts, TikTok, stories, feed and stills — each brand-checked by a specialist that composed none of it.

  6. Media Buyer

    A paper build of the campaign tree — no console, no spend. Blockers surface before you approve.

A ratified campaign plan, a production-ready spec for every placement — the long-form roteiro included — and the launch package your media buyer runs.

Billing, wired into what you already have On the roadmap

Point. Click. Billing live.

Point ForgePlay at your existing codebase: it designs the payment flow, implements the backend logic, builds the checkout UI, locks down compliance, and writes the tests in one coordinated run.

  1. Architecture

    Designs the payment flow and presents the implementation options — you choose, it builds.

  2. API Designer

    Defines the webhook endpoints and the subscription-management contracts.

  3. Backend Engineer

    Implements payment logic, retry handling, and failed-charge recovery.

  4. Frontend Engineer

    Builds the checkout UI and the subscription screens your users actually see.

  5. Security Specialist

    Compliance audit — every endpoint reviewed, every data surface validated.

  6. Testing Engineer

    End-to-end payment tests: happy path, failure scenarios, webhook edge cases.

A working billing integration — subscriptions, webhooks, failed-charge recovery. Tested, reviewed, merged.

The library grows on a rhythm.

ForgePlay is a cadence, not a fixed feature set. New plays land on a regular rhythm — each one a fresh agent chain that turns a goal into shipped work. On the roadmap:

  • On the roadmap firebase-login
  • On the roadmap supabase-auth
  • On the roadmap aws-terraform
  • On the roadmap digitalocean-setup
  • On the roadmap audio-hook (STT / TTS)
  • On the roadmap chat-app-from-zero

Run your first play.

Describe the goal. Watch the specialists work. Keep the output.

Run your first play Back to home