factory
Skill74 starsChanged 38 days agoMITView on GitHub
Launch the Factory CEO agent to autonomously evolve any software project through systematic experimentation. Detects project state, spawns specialist agents, runs evals, and archives learnings.
15 other projects use a version of this.
Adopted by
Most recently taken up by
- lutzseverino/repo-canontheir own version, first seen Nov 8, 2026
- momoathome/software-factorytheir own version, first seen Nov 8, 2026
- WordPress/desktop-modetheir own version, first seen Nov 2, 2026
- BuilderIO/skillstheir own version, first seen Oct 28, 2026
- RTekaya/app-factorytheir own version, first seen Oct 15, 2026
- AirsupHQ/factory-skilltheir own version, first seen Oct 15, 2026
Other versions15 projects use a version of this.
Word for word · 1
- akashgit/remote-factory★ 74100% same
Edited · 0
None found.
Wrote their own version · 14
- PrimeIntellect-ai/prime-agent★ 23ksame name
- BuilderIO/skills★ 4.7ksame name
- WordPress/desktop-mode★ 280same name
- AirsupHQ/factory-skill★ 16same name
- xavierforge/skills★ 4same name
- jaydubya818/MissionControl★ 2same name
- berth-dev/berth★ 1same name
- jircdev/crew-plugin★ 1same name
- lutzseverino/repo-canon★ 1same name
- oleg-koval/factory★ 1same name
4 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository8 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- implementSkill
- pipelineSkill
- pipeline-subagentsSkill
- statusSkill
- studySkill
- workflow-design-v2Skill
The file
We split this skill into the rules it gives an agent
1 rule. 0 are common, 0 are distinctive, and 1 is very specific to this project.
0
Common
Most of the 13 edited versions we read keep these.
0
Distinctive
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 61
All prompts support two-tier override: project-specific (.factory/agents/<role>.md) takes precedence over factory default.
“Common” is measured: kept by at least 6 in 10 of the 13 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Factory Skill v2 — CEO Launcher
This skill spawns the Factory CEO Agent — a dedicated autonomous orchestrator that manages the full factory workflow. The CEO delegates all execution to 7 specialist agents: Researcher, Strategist, Builder, Reviewer, Evaluator, Archivist, and (recursively) itself.
Do not attempt to run the factory workflow yourself. Delegate entirely to the CEO agent.
Usage
# Resolve the factory installation root
FACTORY_HOME="$(factory home)"
# Launch the CEO agent (default: improve mode)
factory ceo "$(pwd)"
# Or specify a mode
factory ceo "$(pwd)" --mode discover # Auto-detect evals
factory ceo "$(pwd)" --mode improve # Improvement loop (default)
factory ceo "$(pwd)" --mode meta # Self-improvement only (ACE)What the CEO Does
- Detects project state — routes to Build, Discover, Review, or Improve mode
- Spawns specialist agents — each gets fresh context with evolved playbooks auto-injected
- Manages experiments — begin, evaluate, implement, guard, evaluate, keep/revert
- Mandatory archival — Archivist fires at every checkpoint (research, strategy, experiment, final)
- Self-learning — CEO decisions feed ACE playbook evolution for all 7 agent roles
Alternative Invocations
# Via factory run (same thing, supports heartbeat loop mode)
factory run /path/to/project --loop --interval 1800
# Via factory agent (invoke any specialist directly)
factory agent researcher --task "Research the project" --project /path
# In a detached tmux session
factory tmux /path/to/project --loopAgent Roles
| Role | Prompt | Purpose |
| CEO | factory/agents/prompts/ceo.md | Orchestrate, decide, delegate |
| Researcher | factory/agents/prompts/researcher.md | Observe, research, synthesize |
| Strategist | factory/agents/prompts/strategist.md | Generate prioritized hypotheses |
| Builder | factory/agents/prompts/builder.md | Implement changes on feature branch |
| Reviewer | factory/agents/prompts/reviewer.md | Guard rules, scope, code quality |
| Evaluator | factory/agents/prompts/evaluator.md | Score before/after, interpret |
| Archivist | factory/agents/prompts/archivist.md | Record learnings to Obsidian vault |
All prompts support two-tier override: project-specific (.factory/agents/<role>.md) takes precedence over factory default. Evolved playbooks from ~/.factory/playbooks/<role>.md (user-local, ACE-generated) are auto-injected, falling back to factory defaults in factory/agents/playbooks/<role>.md.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

