agent-framework

Claude Code plugin providing a structured multi-agent framework with orchestrator, planner, coder, and designer agents plus workflow skills for git branching, commits, PRs, and code review remediation.

Install

Inside Claude Code, add the marketplace then install the plugin:

/plugin marketplace add https://github.com/brenpike/agent-framework.git
/plugin install agent-framework@brenpike

Per-project setup

1. Enable the plugin and set the orchestrator as the session default agent in .claude/settings.json:

{
  "enabledPlugins": {
    "agent-framework@brenpike": true
  },
  "agent": "agent-framework:orchestrator"
}

The agent key sets the default agent for the project session. Without it, Claude Code starts with the default agent and the orchestrator is only reachable on-demand via the Agent tool — bypassing the workflow guarantees.

Or run the setup skill once to apply the required keys automatically:

/agent-framework:setup-project

The setup skill also adds .agent-framework/ to your project's .gitignore. This directory is created at runtime by the orchestrator for ephemeral plans, handoffs, and checkpoints — it should not be committed. If you prefer manual setup, add .agent-framework/ to your project's .gitignore directly.

2. Create CLAUDE.md with project-specific details:

   • Build/test commands
   • Package names and version file paths
   • Versioning configuration (bump triggers, changelogs, tag prefixes)
   • Architecture and code style notes

3. Create AGENTS.md at the project root with project-specific Codex review guidance. Use plugin/governance/AGENTS.template.md as a starting point and adapt:

   • Review focus areas
   • Severity definitions
   • Project-specific conventions for reviewers

Once configured, the orchestrator is the session default agent. All skills are available namespaced as agent-framework:<skill-name>.

Recommended companion plugins

• claude-mem — provides the optional claude-mem:mem-search skill referenced by the planner for cross-session memory and continuity. Install separately as a Claude Code plugin. The agent framework works without it; if installed, planning invokes claude-mem:mem-search before every plan unless the repo has zero commits or the user explicitly opts out.

After cloning a project that uses this plugin

/plugin marketplace add https://github.com/brenpike/agent-framework.git
/plugin install agent-framework@brenpike

Repository layout

.claude-plugin/
  marketplace.json          # marketplace manifest (lives at repo root; points to ./plugin)
plugin/                     # plugin root — everything Claude Code loads lives here
  .claude-plugin/
    plugin.json             # plugin manifest
  agents/                   # agent definitions
  skills/                   # skill definitions (incl. _shared/ helpers)
  governance/               # runtime governance docs loaded via ${CLAUDE_PLUGIN_ROOT}/governance/
docs/
  planning/                 # advisory planning material and implementation backlog — not active plugin governance
tools/                      # dev-only validation scripts (policy linter, report validator)
tests/                      # dev-only test fixtures and checks (policy, reports, plugin compatibility)
README.md

plugin/governance/ is the active runtime governance directory. Agents and skills reference these files via ${CLAUDE_PLUGIN_ROOT}/governance/ paths; they are loaded at runtime and affect agent behavior.

docs/planning/ contains advisory planning material — state machine drafts, report examples, rule index drafts, glossary stubs, and the improvement backlog. These documents are human and dev-tooling reference only; they are not referenced by agents or skills and are not part of the installed plugin.

tools/ and tests/ contain development-time validation scripts and test fixtures. They live outside plugin/ and are not distributed as plugin runtime data.

${CLAUDE_PLUGIN_ROOT} resolves to the plugin/ directory at runtime, so all internal cross-references (e.g. ${CLAUDE_PLUGIN_ROOT}/governance/agent-system-policy.md) resolve correctly without per-consumer configuration.

Agents

Agent	Role
agent-framework:orchestrator	Default agent. Coordinates all work, owns git workflow, branch/PR decisions, versioning decisions, and external review routing.
agent-framework:planner	Research and implementation planning. Read-only — no file writes.
agent-framework:coder	Implementation within explicitly assigned file scope.
agent-framework:designer	Presentational UI/UX work within explicitly assigned file scope.

Skills

All skills are invoked using the namespaced form:

Skill	Purpose
agent-framework:setup-project	One-time project setup: write required .claude/settings.json keys (enabledPlugins + default agent) and add .agent-framework/ to .gitignore
agent-framework:create-working-branch	Create or confirm a compliant working branch before implementation
agent-framework:checkpoint-commit	Commit a completed phase, milestone, version bump, or review-remediation item
agent-framework:open-plan-pr	Open a pull request after completion, validation, and versioning gates pass
agent-framework:address-pr-feedback	Fix a specific generic or human PR comment (one-time)
agent-framework:request-codex-review	Request Codex review on an existing pushed PR
agent-framework:watch-pr-feedback	Monitor a PR for new review feedback and route to remediation skills

Governance

Reference documentation in plugin/governance/:

File	Contents
agent-system-policy.md	Cross-agent constraints, authority matrix, allowed agent topology
branching-pr-workflow.md	Branch taxonomy, naming rules, commit and PR policy
pr-review-remediation-loop.md	External PR review feedback handling and classification
versioning.md	SemVer rules, bump triggers, changelog and tag policy
AGENTS.template.md	Template for project-specific Codex reviewer guidance

Governance rules are embedded in agent definitions. These files are reference material for humans and for agents that need to re-read specific rules.

Plugin limitations

The following agent frontmatter fields are not supported by the Claude Code plugin system and are omitted from plugin agent definitions:

• mcpServers — configure MCP servers at the project or global level instead
• permissionMode — read-only enforcement is achieved by limiting the planner's tools frontmatter to read-only commands; see the planner's tools list in plugin/agents/planner.md

License

MIT