agentleFS
boston-harness-groupboston-harness-group/remote-factory/SKILL.md

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

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
  1. Very specific:

    All prompts support two-tier override: project-specific (.factory/agents/<role>.md) takes precedence over factory default.

    line 61

“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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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

  1. Detects project state — routes to Build, Discover, Review, or Improve mode
  2. Spawns specialist agents — each gets fresh context with evolved playbooks auto-injected
  3. Manages experiments — begin, evaluate, implement, guard, evaluate, keep/revert
  4. Mandatory archival — Archivist fires at every checkpoint (research, strategy, experiment, final)
  5. 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 --loop

Agent Roles

RolePromptPurpose
CEOfactory/agents/prompts/ceo.mdOrchestrate, decide, delegate
Researcherfactory/agents/prompts/researcher.mdObserve, research, synthesize
Strategistfactory/agents/prompts/strategist.mdGenerate prioritized hypotheses
Builderfactory/agents/prompts/builder.mdImplement changes on feature branch
Reviewerfactory/agents/prompts/reviewer.mdGuard rules, scope, code quality
Evaluatorfactory/agents/prompts/evaluator.mdScore before/after, interpret
Archivistfactory/agents/prompts/archivist.mdRecord 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.

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.