Unit 1: Getting started

Tour the factory floor

Lesson 48 min

What we’ll cover

The files that define your factory: factory.yaml and its blueprint, workers, stages, automations, runners, and skills for the inner loop, plus scorers and benchmarks for the outer loop.

Now that you're set up, let's walk through the factory configuration. This is the set of code files (yaml and markdown for the most part) that define every aspect of your factory:

  • The factory.yaml that defines your factory blueprint
  • The automations that bring work into the factory
  • The skills that teach workers how to accomplish tasks
  • The workers that handle factory tasks
  • The runners that define each worker's working environment
  • The scorers that measure the quality of your agents to suggest improvements to the factory (more on this in Unit 3)

Click through this interactive guide of the files to understand their structure, and hover over properties if you're curious to learn more about how Warp Factories handles them:

Factory definition

The factory.yaml sets the core configuration for the factory, including connected repositories, integrations, and model defaults. At the bottom is the blueprint: a state machine that defines every stage a task moves through (like triage, spec, implement, and handoff), which worker owns each stage, and the conditions for moving from one stage to the next.

factory.yamlyaml
schemaVersion: v1alpha2
name: Markdown App Factory
alias: markdown-app-factory
credentialStrategy: EXECUTOR
codeForges:
- GITHUB
repositories:
- owner: YOUR_GITHUB_ORG
name: my-markdown-app
integrations: []
agentDefaults:
model: glm-5.3-flash-fireworks
runner: default
blueprint:
worker: foreman
start:
to: triage
stages:
triage:
worker: builder
prompt:
file: stages/triage.md
to:
- stage: spec
when: A spec is needed, or the requester asked for one.
- stage: implement
when: The goal is a change, and no spec is needed.
spec:
worker: builder
prompt:
file: stages/spec.md
to:
- stage: implement
when: The requester approved the spec.
implement:
worker: builder
prompt:
file: stages/implement.md
to: handoff
handoff:
worker: foreman
prompt: Deliver the PR to the requester.
to: end

What comes next

Now that we understand how our factory is configured, let's start pushing real work through it. In Unit 2, we'll strip our blueprint down to a simple implementation stage and build our factory workflow step by step.