Software Factory — PRs you review in two minutes

The Software Factory is a team of three agents that works your GitHub repository from a Ghosty Teams room. You write what you need the way you'd tell a person and sign twice: the plan and the PR. They do the rest.

Writing code is cheap now; reviewing it isn't. So the factory isn't measured by how many PRs it opens but by how many you approve on the first pass: every PR arrives with its risk, what to read first and how it looks.

The roles

Each role is a Studio agent you choose (engine, model and keys are changed in /app/agents). The same agent can be @ghosty in another room and @build here: the role reaches it per turn. A @check on a different engine than @build reviews better, because it doesn't share its blind spots.

Install

1. Teams → Settings → Apps → Software Factory (workspace owner only).
2. Pick the repo and which Studio agent plays each role. Connect your GitHub to sign.
3. The factory room and its Tasks board are created. Every room with repos is a factory: you can bind more repos to other rooms.
4. In /factory, "Ready for agents" grades the repo and "Prepare repo" opens a single PR with what's missing: CI, AGENTS.md, CODEOWNERS and Dependabot. With GitHub Pro or Team (or a public repo), "Protect main" turns on the rule that nothing gets in without approval.

Ask for a change

@plan add exporting appointments to CSV from the calendar

1. @plan posts the plan card. Sign it with the button, with "✅" in the thread, or ask for changes with "cambios: …".
2. Once signed, @build builds with your GitHub and opens a draft PR.
3. @check reviews it. If it passes, the platform takes the PR out of draft and posts the verdict card.
4. You review and merge (from the card or on GitHub). The request closes by itself when merged.

Other ways in: assign a task to @plan in Tasks, "What do you want to achieve?" in /factory (it splits it into a sprint of 3 to 8 tickets), "Suggest requests" and scheduled reviews in "Automatic".

The verdict card

What you need to review in two minutes, without rebuilding the change in your head:

• Risk. The platform marks it from what the PR touches, not from the agent's word: authentication, migrations, dependencies, public API, .github/ or more than 400 lines → high. @check can raise it for delicate logic, never lower it.
• Read first. Up to five file:lines with the why, most delicate first.
• Screenshots. If the repo has previews, the screen that changed on desktop and mobile.
• Changes, CI and review: files and lines, CI status (verified on GitHub) and how many rounds it took with @check.
• Details: what @check said, folded.

What's measured

In /factory, per room:

Next

• Team per repo: .ghosty/factory.md and "@build con opus".
• Knowledge base: what agents must know about your repo, in your repo.
• Evals: compare agents and models on your own requests.