# AI use cases for Eve Software Factory Template (vercel-labs/eve-software-factory-template) Repo: [vercel-labs/eve-software-factory-template](https://github.com/vercel-labs/eve-software-factory-template) | Use cases: 4 | Page: https://dedupedai.com/use-cases/vercel-labs-eve-software-factory-template/ Foreman is an open template for an AI software factory that takes tasks from GitHub and Linear, runs them through four AI agent stations, and delivers a reviewed draft pull request for a person to review and merge. This file holds every use case of this repo. Each one starts with a "## " heading and ends with its URL. - Turn a labeled GitHub issue into a reviewed draft PR: https://dedupedai.com/use-cases/vercel-labs-eve-software-factory-template/label-issue-for-draft-pr/ - Run a factory task from your machine with the dev TUI: https://dedupedai.com/use-cases/vercel-labs-eve-software-factory-template/hand-task-to-factory-locally/ - Delegate a Linear task to the factory and track it in Linear: https://dedupedai.com/use-cases/vercel-labs-eve-software-factory-template/delegate-linear-task-to-factory/ - Have the factory fix red CI on its own draft PRs: https://dedupedai.com/use-cases/vercel-labs-eve-software-factory-template/auto-fix-red-ci-on-factory-prs/ ## How to turn a labeled GitHub issue into a reviewed draft PR with Eve Software Factory Template Repo: [vercel-labs/eve-software-factory-template](https://github.com/vercel-labs/eve-software-factory-template) | Difficulty: Intermediate | Time: 60 minutes | Basis: From the README Label an issue factory and get a reviewed draft pull request to review and merge. **Who it is for:** A maintainer or developer with a backlog of small, well-described GitHub issues who wants a first draft of each change without writing it by hand. **The problem:** Routine issues sit in the queue because writing the plan, the code, and the first pass of checks takes time that the team does not have. **The outcome:** Each labeled issue produces a draft PR on the target repository, linked to the issue, with progress comments along the way. A person reviews it, marks it ready, and merges. ### Steps 1. Click the Deploy button in the README and set FACTORY_REPO to your owner/repo. 2. Install the GitHub App behind the GitHub connector on that repository so it has access. 3. Open an issue on the repository with a clear description of the change. 4. Add the factory label to the issue (default label: factory). 5. Review the draft PR linked to the issue, then mark it ready and merge it. ### Prompt to paste into your agent ```text Work on the GitHub repository using the factory label on issue . Confirm the factory opens a draft pull request linked to the issue, and check that the draft PR's CI runs and reports a result before anyone marks it ready. ``` ### Caveat A station's sandbox clones FACTORY_REPO on its first session, so an unreachable repository shows up as a Cannot access error on the first task, not at deploy time. Risk, credentials: The GitHub App you install gives the factory access to push branches and open pull requests on the repository you select, so limit the install to the repositories you intend. Disclaimer: Third-party repos we don't own or vouch for. AI-generated use cases can be wrong: review everything and run at your own risk. Full text: https://dedupedai.com/disclaimer/ URL: https://dedupedai.com/use-cases/vercel-labs-eve-software-factory-template/label-issue-for-draft-pr/ ## How to run a factory task from your machine with the dev TUI with Eve Software Factory Template Repo: [vercel-labs/eve-software-factory-template](https://github.com/vercel-labs/eve-software-factory-template) | Difficulty: Intermediate | Time: 30 minutes | Basis: From the README Give the factory a task from your terminal and approve changes before they reach GitHub. **Who it is for:** A developer who wants to try the factory on a task locally before trusting it with issues in a shared repository. **The problem:** Teams want to see what the agents produce for a real task before turning on the labeled-issue flow for everyone. **The outcome:** The four stations run in order on a task you give in the TUI, and you approve any changes before they are written to GitHub. ### Steps 1. Run `vercel link` to link the deployed project or a fresh one. 2. Run `vercel env pull` to pull the project environment. 3. Run `pnpm dev` to start the TUI. 4. Give the agent a task in the TUI, such as a small bug report. 5. Watch the Classifier, Analyst, Implementer, and Reviewer stations, then approve or reject the changes sent to GitHub. ### Prompt to paste into your agent ```text In the eve-software-factory-template project, run `vercel link`, `vercel env pull`, and `pnpm dev`, then give the factory the task . Verify that the four stations run in order and that no change reaches GitHub until you approve it in the TUI. ``` ### Caveat The README says local runs are treated as untrusted, so the TUI is the safe place to test before turning on the labeled-issue flow. Disclaimer: Third-party repos we don't own or vouch for. AI-generated use cases can be wrong: review everything and run at your own risk. Full text: https://dedupedai.com/disclaimer/ URL: https://dedupedai.com/use-cases/vercel-labs-eve-software-factory-template/hand-task-to-factory-locally/ ## How to delegate a Linear task to the factory and track it in Linear with Eve Software Factory Template Repo: [vercel-labs/eve-software-factory-template](https://github.com/vercel-labs/eve-software-factory-template) | Difficulty: Intermediate | Time: 60 minutes | Basis: From the README Assign a Linear task to the factory and follow its progress inside Linear. **Who it is for:** A product or engineering lead who tracks work in Linear and wants a task built without leaving Linear. **The problem:** Work tracked in Linear has to be copied into GitHub by hand before any code work starts, which slows the handoff. **The outcome:** The Linear Agent Session runs the same pipeline and reports progress back in Linear, ending in a draft PR on the repository. ### Steps 1. Connect the Linear connector during the Vercel deploy flow. 2. Confirm FACTORY_REPO names a repository the GitHub App can access. 3. Delegate a Linear issue to the factory agent in Linear. 4. Follow the progress reports posted back in Linear as each station completes. 5. Open the draft PR on FACTORY_REPO, review it, mark it ready, and merge it. ### Prompt to paste into your agent ```text Delegate the Linear issue to the factory for the repository . Verify that progress updates appear in the Linear issue and that the run ends with a draft pull request on . ``` ### Caveat The README describes Linear delegation as running the same pipeline, so the same repository access rules apply, and the draft PR still needs a human to review and merge it. Risk, credentials: The Linear connector and the GitHub App give the factory access to your Linear workspace and your repository, so grant only the access the team needs. Disclaimer: Third-party repos we don't own or vouch for. AI-generated use cases can be wrong: review everything and run at your own risk. Full text: https://dedupedai.com/disclaimer/ URL: https://dedupedai.com/use-cases/vercel-labs-eve-software-factory-template/delegate-linear-task-to-factory/ ## How to have the factory fix red CI on its own draft PRs with Eve Software Factory Template Repo: [vercel-labs/eve-software-factory-template](https://github.com/vercel-labs/eve-software-factory-template) | Difficulty: Advanced | Time: 90 minutes | Basis: From the README Let Foreman diagnose a failing check on a factory PR and push the fix to its own branch. **Who it is for:** A maintainer who runs the factory on a busy repository and wants failing checks on factory branches repaired without manual edits. **The problem:** A draft PR from the factory fails CI, and someone has to read the logs and push a fix before review can continue. **The outcome:** Foreman diagnoses the failure and pushes a fix to its own factory branch, leaving your branches alone. ### Steps 1. Confirm FACTORY_BRANCH_PREFIX is set to the default factory/ or your chosen prefix. 2. Open a draft PR from the factory on a branch that starts with that prefix. 3. Let CI run on the draft PR and wait for a red result. 4. Check the new commit Foreman pushes to its own factory branch. 5. Review the updated draft PR and merge it once CI is green and you approve the change. ### Prompt to paste into your agent ```text On the repository , find the factory draft PR on branch with failing CI. Verify that Foreman pushes its fix to that factory/ branch only and that CI on the PR turns green after the push. ``` ### Caveat The README says automated CI fixes only touch branches with the factory prefix, so a PR on any other branch will not receive an automatic fix. Disclaimer: Third-party repos we don't own or vouch for. AI-generated use cases can be wrong: review everything and run at your own risk. Full text: https://dedupedai.com/disclaimer/ URL: https://dedupedai.com/use-cases/vercel-labs-eve-software-factory-template/auto-fix-red-ci-on-factory-prs/