Factories > Factory use cases
Factory use cases
# Factory use cases Warp Factories can investigate issues, implement approved changes, review pull requests, and verify interfaces with visual evidence. These recipes show how to configure those tasks in your existing factory and where a person decides what happens next. Each recipe combines agents, automations, skills, integrations, and repository controls. The examples use [definitions as code](/factories/factory-as-code/) so you can review and validate changes, or adapt them to a Warp-managed factory. ## Choose a use case <CardGrid> <LinkCard title="Issue triage" href="/factories/use-cases/issue-triage/" description="Return evidence, classification, priority, and a next action without starting implementation." /> <LinkCard title="Code review" href="/factories/use-cases/code-review/" description="Post actionable pull request findings without changing, approving, or merging code." /> <LinkCard title="Issue implementation" href="/factories/use-cases/issue-implementation/" description="Turn approved GitHub, Linear, or Jira issues into validated pull requests for human review." /> <LinkCard title="Production incident resolution" href="/factories/use-cases/production-incident-resolution/" description="Return a read-only incident report, then request a code fix separately." /> <LinkCard title="Computer Use verification" href="/factories/use-cases/computer-use-verification/" description="Return observed UI behavior and visual evidence in a pull request comment." /> <LinkCard title="End-to-end SDLC automation" href="/factories/use-cases/end-to-end-sdlc-automation/" description="Carry an issue through planning, implementation, review, and verification to a human-controlled merge." /> </CardGrid> ## 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](/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](/factories/quickstart/) - Create a factory and send its first work item * [About factory agents](/factories/factory-agents/) - Understand default roles and human decision points * [Factory automations](/factories/automations/) - Route provider events to agents with filters * [Factory definition syntax](/factories/factory-as-code/) - Look up configuration keys and validate definitionsTell me about this feature: https://docs.warp.dev/factories/use-cases/Choose a practical Warp Factories recipe for issue triage, implementation, code review, incident response, UI verification, or SDLC automation.
Warp Factories can investigate issues, implement approved changes, review pull requests, and verify interfaces with visual evidence. These recipes show how to configure those tasks in your existing factory and where a person decides what happens next.
Each recipe combines agents, automations, skills, integrations, and repository controls. The examples use definitions as code so you can review and validate changes, or adapt them to a Warp-managed factory.
Choose a use case
Section titled “Choose a use case”Start with the smallest recipe
Section titled “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.
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
Section titled “Related pages”- Warp Factories quickstart - Create a factory and send its first work item
- About factory agents - Understand default roles and human decision points
- Factory automations - Route provider events to agents with filters
- Factory definition syntax - Look up configuration keys and validate definitions