Agent Plugins Marketplace
← All plugins

polyforge

v1.1.31

polyforge v1 — Go-native multi-agent AI coding coordination. Implements Iron Rules (IR1-IR4), the full wi lifecycle (work/stop/status/spec/plan/execute/retro), and a memory system. Requires the ieops-aihub backend.

CodexClaude Code17 Skills1 MCP serverstdio

By GMI Engineering0 GitHub starsUpdated 2 weeks ago

Directory evidence

Runtimes
Codex and Claude Code
Parsed components
18 skill or MCP entries
Source updated
Sep 10, 2026
Manifest status
Canonical path parsed

The directory validates manifest shape and source location. It does not execute the plugin or provide a security endorsement. Review the indexing methodology →

Install polyforge for Codex and Claude Code

Installs for the current user
codex plugin marketplace add IchenDEV/agent-plugin-mkt
codex plugin marketplace upgrade agent-plugin-marketplace
codex plugin add polyforge@agent-plugin-marketplace

Paste and run these commands in a terminal with Codex. They add and refresh the PluginsMP catalog, then install this plugin.

The installer fetches third-party code from the source repository shown on this page. This directory validates manifest structure and source location, but does not perform a security audit; review the manifest, components, and source before installing.

Get the source manually
git clone https://github.com/GMISWE/ieops-aihub

Clone the source repository, then follow its setup instructions to add the plugin to a compatible client. The plugin root is plugins/polyforge/.

Plugin files

plugins/polyforge/
├── .codex-plugin/plugin.json
├── .claude-plugin/plugin.json
├── skills/pf-crystallize/SKILL.md
├── skills/pf-doctor/SKILL.md
├── skills/pf-execute/SKILL.md
├── skills/pf-help/SKILL.md
├── skills/pf-init/SKILL.md
├── skills/pf-plan/SKILL.md
├── skills/pf-project/SKILL.md
├── skills/pf-release/SKILL.md
├── skills/pf-retro/SKILL.md
├── skills/pf-revise/SKILL.md
├── skills/pf-spec/SKILL.md
├── skills/pf-status/SKILL.md
├── skills/pf-stop/SKILL.md
├── skills/pf-sync/SKILL.md
├── skills/pf-user/SKILL.md
├── skills/pf-work/SKILL.md
├── skills/using-polyforge/SKILL.md
└── .mcp.json

Included Skills17

pf-crystallizeskills/pf-crystallize/SKILL.md

Use when a wi has just been wrapped via /pf-stop --wrap and its operation flow should be captured as a reusable scenario workflow for future wis of the same type. Dispatched automatically by pf-stop --wrap, not invoked directly by the user.

pf-doctorskills/pf-doctor/SKILL.md

Use when the user asks to diagnose or fix the polyforge workspace, MCP connection, repo state, or version mismatch. Also use when any pf-* tool call fails unexpectedly or when onboarding to a new machine.

pf-executeskills/pf-execute/SKILL.md

Use when a claimed wi is ready to be carried out step by step against its scenario step graph, e.g. the user says execute, run it, or go.

pf-helpskills/pf-help/SKILL.md

Use when the user asks how to use a /pf-* skill, what flags it takes, or wants a quick reference of the available polyforge skills.

pf-initskills/pf-init/SKILL.md

Use when setting up a polyforge workspace for the first time on a new machine, adding repos to an existing workspace, refreshing repo descriptions, or repairing a workspace after /pf-doctor reports failures.

pf-planskills/pf-plan/SKILL.md

Use when a claimed wi has a spec and needs an implementation plan broken into ordered steps before coding, or the user says plan, break this down, or create subtasks.

pf-projectskills/pf-project/SKILL.md

Use when the user wants to create, update, or list polyforge projects, or rotate a project access identifier.

pf-releaseskills/pf-release/SKILL.md

Use when the team is ready to cut a versioned alpha release, promote an alpha channel to stable, or check the current release state.

pf-retroskills/pf-retro/SKILL.md

Use when a wi has just been wrapped and its outcome should be reviewed for learnings to save to team memory, whether run standalone or dispatched by /pf-execute. Triggers include retro, lessons learned, and what did we learn.

pf-reviseskills/pf-revise/SKILL.md

Use when a human reviewer has left open annotations on a spec or plan artifact in the /ui viewer and wants the agent to apply that feedback and resolve the annotations.

pf-specskills/pf-spec/SKILL.md

Use when a claimed feature or bug wi needs its scope, non-goals, design, and acceptance criteria defined, or when a bug needs root-cause analysis, e.g. write a spec, scope this out, debug, or root cause.

pf-statusskills/pf-status/SKILL.md

Use when the user wants to know what is happening: progress on a claimed wi, the project ready queue, or which items are stalled, blocked, or need attention.

pf-stopskills/pf-stop/SKILL.md

Use when the user is done working on the current wi and wants to pause it, wrap it as a terminal success, or mark it a terminal failure.

pf-syncskills/pf-sync/SKILL.md

Use when the user wants to sync work items between polyforge and an external tracker such as Jira or GitHub Issues, pulling issues in or pushing a wrapped wi back out.

pf-userskills/pf-user/SKILL.md

Use when the user wants to check their identity, list team members, invite a member, change a user's role, or issue or revoke API keys.

pf-workskills/pf-work/SKILL.md

Use when the user wants to begin working on something: start a new work item, claim a queued one, resume a paused one, or take over a stalled or idle one from another agent.

using-polyforgeskills/using-polyforge/SKILL.md

Use at the start of any polyforge session and before any /pf-* skill, work-item, or memory operation; loaded automatically at session start.

MCP servers1

polyforgestdio
command
./bin/polyforge-mcp.sh
cwd
.

Plugin manifests2

plugins/polyforge/.codex-plugin/plugin.json
{
  "name": "polyforge",
  "version": "1.1.31",
  "description": "polyforge v1 — Go-native multi-agent AI coding coordination. Implements Iron Rules (IR1-IR4), the full wi lifecycle (work/stop/status/spec/plan/execute/retro), and a memory system. Requires the ieops-aihub backend.",
  "author": {
    "name": "GMI Engineering"
  },
  "skills": "./skills/",
  "hooks": "./codex-hooks.json",
  "mcpServers": "./.codex-plugin/mcp.json",
  "keywords": [
    "polyforge",
    "v1",
    "coding",
    "multi-agent",
    "wi-lifecycle"
  ],
  "interface": {
    "displayName": "polyforge",
    "shortDescription": "Multi-agent AI coding coordination with a full work-item lifecycle.",
    "longDescription": "polyforge brings Iron-Rule-governed work-item lifecycle (work / stop / status / spec / plan / execute / retro) and a memory system to Codex. The MCP server auto-registers from this manifest (mcpServers -> .codex-plugin/mcp.json) as a local stdio command; no manual codex mcp add is needed. The Claude Code Skill-router hook is intentionally omitted on Codex (no Skill tool); /pf-spec|plan|execute load their step body from each SKILL.md natively.",
    "developerName": "GMI Engineering",
    "category": "Coding",
    "capabilities": [
      "Read",
      "Write"
    ]
  }
}
plugins/polyforge/.claude-plugin/plugin.json
{
  "name": "polyforge",
  "version": "1.1.31",
  "description": "polyforge v1 — Go-native multi-agent AI coding coordination. Implements Iron Rules (IR1-IR4), three-layer L1/L2/L3 architecture, and the full wi lifecycle (work/stop/status/spec/plan/execute/retro).",
  "author": {
    "name": "GMI Engineering"
  },
  "mcpServers": {
    "polyforge": {
      "command": "${CLAUDE_PLUGIN_ROOT}/bin/polyforge-mcp.sh",
      "cwd": "${CLAUDE_PLUGIN_ROOT}"
    }
  },
  "keywords": [
    "polyforge",
    "v1",
    "coding",
    "multi-agent",
    "wi-lifecycle"
  ],
  "catalog_revision": "2672f471676dc96231fb11b8396737a197183100"
}

For maintainers

If you maintain this plugin, link to this source-backed listing from your README so users can review its manifest and indexed components.

[polyforge on Agent Plugins Marketplace](https://pluginsmp.com/plugins/polyforge)