Stats
Actions
Tags
From factory
Builds a specific feature or improvement using Factory's multi-agent system. Runs the Factory CEO in focus mode to study, build, review, and evaluate changes autonomously.
How this skill is triggered — by the user, by Claude, or both
Slash command
/factory:implement <what to build><what to build>The summary Claude sees in its skill listing — used to decide when to auto-load this skill
Build a specific feature or improvement using the Factory's multi-agent system.
Build a specific feature or improvement using the Factory's multi-agent system.
The user wants to build: $ARGUMENTS
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}"
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:
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.
npx claudepluginhub akashgit/remote-factory --plugin factoryGuides multi-phase feature development with research, planning, implementation, and review phases. Use for complex features touching >5 files or requiring architecture decisions.
Implements features using parallel subagents with scope control, reflection, and MCP servers for memory/context. Activates on implement/build/create requests in JS/TS projects.
Implements features from specs using Codex MCP with iterative review. Breaks work into dependency-ordered items, collects project context, and runs a confirm/reject/modify loop per item.