Factory skill
Software factory installer for Claude Code and Codex: a GitHub Issues queue, skills, gates and merges done only by a human.
- 344 ★ on the repository
- Last commit
- MIT
Extended access
Why this level
- Scheduled routines write code, open draft PRs and change labels with no human until review.
Install
- Works in
Manual install
git clone https://github.com/addyosmani/factory.git
cd /path/to/your/repo
/path/to/factory/install.sh --dry-run .
/path/to/factory/install.sh .The installer never overwrites existing files, so re-running is safe.
Access and checks
How we reviewExtended accessThe tool runs code or makes network calls and only reads external data.
- Scheduled routines write code, open draft PRs and change labels with no human until review.
This is third-party code. Review the repository files before installing.
What it does
Factory installs rules and skills into an existing GitHub project so that Issues become a work queue. Scheduled runs triage new issues, pick up permitted small work, implement it on a branch and open draft PRs. Type, lint, test and build checks run first, and an independent verifier reads the diff cold. The rules live in the repository: `docs/factory/CHARTER.md` sets autonomy level and protected paths, `gates.sh` emits the check verdict, and `/factory` shows what awaits a human. A Codex layer mirrors the same skills.
Who it is for. Team leads and GitHub project owners who want an agent to take small tasks regularly and return draft PRs with evidence.
Good fit when
- Small tasks pile up in GitHub Issues and triaging them by hand takes too long.
- An independent verifier agent should read the work before a PR opens.
- The agent's autonomy should be limited by a charter and a review queue cap.
- The same rules should apply in Claude Code and in Codex.
Not a fit when
- A plain Claude Code or Codex session is enough; the README advises starting there.
- You want auto-merge: Factory never merges at any tier.
- The project is not hosted on GitHub.
Example request
Run /factory-triage on new Issues and show which tasks qualify for autonomous implementation under the charter.Limitations
Claude cloud routines have no trigger for new Issues, so the template polls the queue on a schedule; instant triage needs an extra GitHub Action. The repository creates no schedules for Codex. Hooks block common merge routes, but the security boundary is GitHub rules, so configure branch protection. The last commit dates from August 2026. Runs start from a fresh clone, so rules must be committed rather than kept in the home `~/.claude/` folder.
How to disable. Remove `docs/factory/`, `.factory/`, the `factory-*` skills, agents and hooks from `.claude/` and `.agents/`, then disable routines and the `factory:*` labels. The installer never overwrites files, so changes are easy to separate.
FAQ
Does Factory merge PRs itself?
No. Merging stays with a human at every tier, and branch protection is enforced through GitHub rules.
How does the verifier differ from the writer?
It reads the diff cold and rejects when uncertain. Its best check is reverting the fix to confirm the test fails.
What limits the flow of PRs?
The `STOP_IF` setting in the charter. When the review queue is full, the implementation routine refuses to start.
Does it work in Codex?
Yes, interactively, through `AGENTS.md` and skills in `.agents/skills/`. The README describes unattended schedules only for Claude cloud routines.
Where does the installer put files?
Into the target repository: `docs/factory/`, `.factory/`, and skills and agents under `.claude/` and `.agents/`. It never overwrites files, and `--dry-run` shows the plan first.
Discussion
No questions or reviews yet.
Related
SkillsFactory Factory runs Claude Code and Codex in parallel, each in its own git worktree, with diffs and terminal in one window.
A skill for Codex and Claude Code that turns ideas and bugs into working code through a writer, tester and reviewers
A ready harness for Claude Code and Codex: spec-driven development, TDD, memory between sessions, quality gates and human checkpoints
A CLI and Claude Code plugin taking GitHub issues through checks, plan, code, review and CI to merge, in parallel lanes
A Claude Code skill that drives Codex over JSON-RPC: tasks, code reviews, parallel research and messaging between two agents.
A skill that runs an eight-step loop: Claude orchestrates and arbitrates while Codex writes, critiques and fixes the code.
README in short
The factory lives in the repository: charter, queue contract, gate script, skills and agents. Cloud routines supply the clock and GitHub holds the queue.
README badge
Original SKILL.md
--- name: factory-triage ---