> For the complete documentation index, see [llms.txt](https://docs.warp.dev/llms.txt).
> Markdown versions of each page are available by appending .md to any URL.

# Factory use cases

Choose a practical Warp Factories recipe for issue triage, implementation, code review, incident response, UI verification, or SDLC automation.

A recipe is a recommended configuration and set of instructions for completing a specific task with your factory. It combines agents, automations, integrations, skills, and repository controls. You can start with one task and test its results before connecting it to another. For example, your team might try issue triage on its own before asking the factory to implement approved issues.

The examples use [definitions as code](https://docs.warp.dev/factories/factory-as-code/) so you can review changes, validate them in CI, and adapt the same pattern to a Warp-managed factory.

## Choose a use case

[Issue triage](https://docs.warp.dev/factories/use-cases/issue-triage/)Investigate, categorize, and prioritize incoming issues.

[Code review](https://docs.warp.dev/factories/use-cases/code-review/)Review pull requests and return actionable findings.

[Issue implementation](https://docs.warp.dev/factories/use-cases/issue-implementation/)Turn approved GitHub, Linear, or Jira issues into tested pull requests.

[Production incident resolution](https://docs.warp.dev/factories/use-cases/production-incident-resolution/)Investigate production signals and propose or implement a fix.

[Computer Use verification](https://docs.warp.dev/factories/use-cases/computer-use-verification/)Exercise a rendered interface and attach visual evidence.

[End-to-end SDLC automation](https://docs.warp.dev/factories/use-cases/end-to-end-sdlc-automation/)Connect triage, implementation, review, and verification with human gates.

## Start with the smallest recipe

One factory can coordinate work across repositories that ship together. Before you add an automation, choose the event that should start work and check whether an existing automation already handles it. You can update that automation instead of adding another, or use nonoverlapping filters when you need separate automations. See [automation matching rules](https://docs.warp.dev/factories/automations/#how-matching-works).

Each automation needs a clear task, a responsible agent, and an expected output. For work that spans several roles, the foreman coordinates the other agents. Your skills supply repository-specific procedures, such as required test commands or an incident runbook. People remain responsible for approving specifications, accepting risk, and merging changes.

## Related pages

-   [Warp Factories quickstart](https://docs.warp.dev/factories/quickstart/) - Create a factory and send its first work item
-   [Factory agents](https://docs.warp.dev/factories/factory-agents/) - Configure the default roles and add custom agents
-   [Factory automations](https://docs.warp.dev/factories/automations/) - Route provider events to agents with filters
-   [Factory definition syntax](https://docs.warp.dev/factories/factory-as-code/) - Look up configuration keys and validate definitions