agentleFS
Sign inStart free
akashgitakashgit/remote-factory/skills/implement/SKILL.md

implement

Skill74 starsChanged 38 days agoMITView on GitHub

Build a specific feature or improvement using Factory's multi-agent system. Runs the Factory CEO in focus mode to study the codebase, generate a hypothesis, build the change, review it, and evaluate the result. Use when the user says 'implement X', 'build X', 'add X feature', or wants autonomous multi-agent development on a specific task.

191 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use setup-ts-deep-modules, ask-matt and 10 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • liufeng1976Skill

    setup-ts-deep-modules

    Wire dependency-cruiser into a TypeScript repo so each package is a deep module — implementation hidden in subfolders, reachable only through its entry-point files. User-invoked.

    Also in 43 projects that use this

  • GoogleSkill

    ask-matt

    Ask which skill or flow fits your situation. A router over the skills in this repo.

    Also in 91 projects that use this

  • RoentekSkill

    loop-me

    Grill me about specs for the workflows I want to build, within this workspace.

    Also in 50 projects that use this

  • AWSSkill

    to-questionnaire

    Turn a decision you can't fully answer into a questionnaire for someone else to fill in.

    Also in 88 projects that use this

  • ryotaroh180105Skill

    claude-handoff

    Hand the current conversation off to a fresh background agent that picks up the work immediately.

    Also in 42 projects that use this

  • GoogleSkill

    to-spec

    Turn the current conversation into a spec and publish it to the project issue tracker — no interview, just synthesis of what you've already discussed.

    Also in 168 projects that use this

  • +3 more from google

The file

We split this skill into the rules it gives an agent

3 rules. 0 are common, 2 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 170 edited versions we read keep these.

  • 2

    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. Distinctive:

    Run the Factory CEO in focus mode on the current project:

    line 26
  2. Distinctive:

    Evaluate: before/after scores to verify improvement

    line 38
  3. Very specific:

    If factory cannot be installed (e.g.

    line 44

“Common” is measured: kept by at least 6 in 10 of the 170 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:implement

Build a specific feature or improvement using the Factory's multi-agent system.

The user wants to build: $ARGUMENTS

Prerequisites

The factory CLI must be installed. Check and install from the plugin's bundled source:

command -v factory >/dev/null 2>&1 || uv tool install "${CLAUDE_PLUGIN_ROOT}"

Execution

The project must have .factory/ initialized (run factory ceo "$(pwd)" or /factory:study first). Focus mode requires improve mode — it will error if the project hasn't been set up yet.

Run the Factory CEO in focus mode on the current project:

factory ceo "$(pwd)" --focus "$ARGUMENTS"

This will:

  1. Study the codebase and generate observations
  2. Strategize a single targeted hypothesis for "$ARGUMENTS"
  3. Build the change on a feature branch with a PR
  4. Review the change against guard rules and scope constraints
  5. Evaluate before/after scores to verify improvement
  6. Keep or revert based on eval results and precheck gates
  7. Archive learnings for future cycles

If the CLI is not available

If factory cannot be installed (e.g. no uv available), tell the user:

To use /factory:implement, install the Factory CLI:

  uv tool install /path/to/remote-factory
  # or from git
  uv tool install git+https://github.com/akashgit/remote-factory

Then re-run this command.

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.

Check your setup, free