Templates

28 complete factories, each teaching one idea. Copy one into your repository with its command: your repository and GitHub login are filled in from gh. Then read the plan, and apply. Templates combine: take agents and automations from several.

Category

28 templates found

Getting started

The whole format in a few files, then the full flow from issue to pull request.

The workflow of At a glance
00

At a glance

The whole format in a few files: issues and production errors become pull requests, failed deploys become issues.

issue.labeledSentrya webhook

3 agents3 automations

openfabriq init --example 00-at-a-glance
The workflow of Quickstart
01

Quickstart

A maintainer labels an issue, an agent opens a pull request and changes it on a comment that mentions @openfabriq.

issue.labeledpull_request.commented

1 agent3 automations

openfabriq init --example 01-quickstart
The workflow of SDLC, from issue to ready pull request
02

SDLC, from issue to ready pull request

The full flow: triage, investigation, implementation reviewed adversarially before the pull request exists, conflicts resolved, with checks and screenshots as proof.

Issuespull requestsSentry

4 agents7 automations

openfabriq init --example 02-sdlc
The workflow of A large factory, ordered by area
04

A large factory, ordered by area

A dozen agents ordered by area: delivery at the root, then qa/, maintenance/ and security/, each folder with its agents and their automations.

Issuespull requestsschedules

11 agents11 automations

openfabriq init --example 04-large-factory

Review and quality

Reviews, red checks, bugs proven by a test, changes checked in a real browser.

The workflow of Code review, advisory only
05

Code review, advisory only

An advisory reviewer on every pull request, on another model.

pull_request.openedpull_request.updated

1 agent1 automation

openfabriq init --example 05-code-review
The workflow of Bug reproducer
07

Bug reproducer

Proves a bug with a failing test before anyone fixes it.

issue.labeled needs-repro

1 agent1 automation

openfabriq init --example 07-bug-reproducer
The workflow of Nightly test coverage
08

Nightly test coverage

Adds behavioral tests to the least-tested module, every night.

schedule

1 agent1 automation

openfabriq init --example 08-test-coverage
The workflow of UI check in a real browser
09

UI check in a real browser

Checks a pull request's change in a real browser, including phone width and keyboard.

pull_request.labeledissue.labeled

1 agent2 automations

openfabriq init --example 09-ui-check

Maintenance

The work nobody schedules: dependencies, docs, release notes, triage, security.

The workflow of Dependency updates, once a week
11

Dependency updates, once a week

Safe minor and patch updates in one pull request; major updates listed for a human.

schedule, Monday

1 agent3 automations

openfabriq init --example 11-dependency-updates
The workflow of Issue triage, a first answer in minutes
14

Issue triage, a first answer in minutes

Classifies, prioritizes and answers new issues; asks for what is missing.

issue.openedissue.commented

1 agent2 automations

openfabriq init --example 14-issue-triage
The workflow of Weekly security audit
15

Weekly security audit

Weekly dependency audit and review of attack surfaces.

schedule, Monday

1 agent1 automation

openfabriq init --example 15-security-audit
The workflow of Security review, with a verifier
16

Security review, with a verifier

A mapper picks the riskiest surfaces, a hunter per surface looks for flaws, a verifier on a stronger model tries to disprove each one.

schedule, Mondayissue.labeled

3 agents3 automations

openfabriq init --example 16-security-review
The workflow of Factory tuner
17

Factory tuner

Reads what people did with the factory's pull requests and proposes one change to an agent's brief a week, with the evidence.

schedule, Monday

2 agents2 automations

openfabriq init --example 17-factory-tuner
The workflow of Tech debt sweeper
18

Tech debt sweeper

One small mechanical cleanup per pull request.

issue.labeled choreschedule

1 agent2 automations

openfabriq init --example 18-tech-debt-sweeper
The workflow of A living wiki
19

A living wiki

Keeps a map of the code in wiki/ after each merge; a guide answers questions from it, the implementer starts from it.

issue.labeled questionready-for-agentafter each merge

2 agents2 automations

openfabriq init --example 19-living-wiki
The workflow of SEO audit
20

SEO audit

A monthly SEO audit of the built site, with no paid service: safe fixes as a pull request on a label, the words left to a person.

schedule, monthlyissue.labeled seo-fixpull_request.labeled

2 agents4 automations

openfabriq init --example 20-seo-audit

Integrations

Work that starts in Slack, in Sentry or from any service that sends a webhook.

The workflow of Slack codebase Q&A
21

Slack codebase Q&A

Answers questions about the code in Slack, read-only; files issues on request.

slack.mentioned

1 agent1 automation

openfabriq init --example 21-slack-codebase-qa
The workflow of Linear delivery
22

Linear delivery

A Linear label gets an implementation plan in the issue; assigning the issue to openfabriq gets a pull request.

linear.issue.labeled needs-planlinear.issue.delegated

2 agents2 automations

openfabriq init --example 22-linear-delivery
The workflow of Sentry autofix
23

Sentry autofix

A new production error becomes a fix with a regression test, using Sentry's MCP server.

sentry.issue.created

1 agent1 automation

openfabriq init --example 23-sentry-autofix
The workflow of Deploy failure webhook
24

Deploy failure webhook

A failed deploy or a downtime alert becomes an incident issue, or a revert.

webhook.received

1 agent2 automations

openfabriq init --example 24-deploy-failure-webhook

Projects

Long projects driven by labels, such as a whole site migration.

The workflow of WordPress maintenance
25

WordPress maintenance

Keeps a Composer-managed WordPress site up to date and safe: weekly updates, a daily WPScan watch, a fix per new vulnerability.

scheduleissue.labeled security-fix

2 agents5 automations

openfabriq init --example 25-wordpress-maintenance
The workflow of Webflow to Astro, leaving Webflow without freezing the content
26

Webflow to Astro, leaving Webflow without freezing the content

Moves a Webflow site to Astro from one plan you merge, each page checked against the old one before its pull request opens, while editors keep writing in Webflow, with a weekly content sync.

A label on a migration issuepushes to the default branchpull requests

3 agents5 automations

openfabriq init --example 26-webflow-to-astro
The workflow of Framer to Astro, leaving a site that exports no code
27

Framer to Astro, leaving a site that exports no code

Moves a Framer site, which exports no code, to Astro from one plan you merge: the agents read the published pages and a CMS export, check each page against the old one before its pull request opens, and hold no Framer key.

A label on a migration issuepushes to the default branchpull requests

3 agents5 automations

openfabriq init --example 27-framer-to-astro

What the templates share

A few practices worth keeping in a factory of your own.

Least privilege
A reviewer cannot push, a triager has tools: [read], and labels are restricted (add_labels: [ready-to-merge]).
Stop and ask
Every agent that might otherwise guess has a step that says: when something is unclear, ask, add needs-info, and stop.
Ready, and how risky
A reviewer that finds nothing blocking adds ready-to-merge and one of risk:low, risk:medium, risk:high, with a Risk: line that says what to look at. needs-human keeps one meaning: the engine gave up, and a person takes over.
A different model for review
Reviewers run on opus when the factory runs on sonnet: a different model does not share the author's blind spots.
Proof in the pull request
The engine runs the checks, and the browser-evidence skill covers what shows on screen.
No duplicates without GitHub access
Agents cannot search other issues or pull requests. Templates that run on a schedule say so in their prompts, and avoid duplicates with a file in the repository or a stable fingerprint in titles.