Emasoft Programmer Agent (EPA)
Version: 1.0.0
Overview
The Emasoft Programmer Agent is a general-purpose programmer that executes implementation tasks assigned by the Orchestrator. It handles the actual coding work across multiple programming languages and toolchains.
Prefix: epa- = Emasoft Programmer Agent
Core Responsibilities
- Code Implementation: Write and modify source code according to specifications
- Test Writing: Create comprehensive test suites
- Code Fixing: Resolve bugs and linting/type errors
- Documentation: Write inline documentation and docstrings
- Multi-Language Support: Work across Python, JavaScript, Rust, Go, and compiled languages
Components
Agent (1)
| Agent | File | Description |
|---|
epa-programmer-main-agent | agents/epa-programmer-main-agent.md | Main general-purpose programmer agent |
Skills (5)
| Skill | Description |
|---|
epa-task-execution | Execute programming tasks per requirements |
epa-orchestrator-communication | Communication with the Orchestrator (EOA) agent |
epa-github-operations | Git and GitHub operations (clone, branch, commit, PR) |
epa-project-setup | Initialize project configuration and install tooling |
epa-handoff-management | Create and receive handoff documents and bug reports |
Hooks
None. The hooks/hooks.json is empty -- EPA uses globally installed hooks.
Scripts (1)
| Script | Description |
|---|
validate_plugin.py | Plugin structure validator |
Workflow
The Programmer Agent follows Steps 14, 15, 17-19, 21-23 from the master workflow:
- Step 14: Receive task from Orchestrator via AI Maestro
- Step 15: Investigate code context using SERENA MCP
- Step 17: Implement changes using Edit tool (NOT scripts)
- Step 18: Run language-specific linter/formatter/type checker
- Step 19: Write/update tests for changed code
- Step 21: Run tests and capture results to timestamped log
- Step 22: If tests fail, delegate to code fixer and repeat
- Step 23: Report completion to Orchestrator with file paths
Installation (Production)
Role plugins are installed with --scope local inside the specific agent's working directory (~/agents/<agent-name>/). This ensures the plugin is only available to that agent.
# Add Emasoft marketplace (first time only)
claude plugin marketplace add emasoft-plugins --url https://github.com/Emasoft/emasoft-plugins
# Install plugin (--scope local = this agent's directory only, recommended)
claude plugin install emasoft-programmer-agent@emasoft-plugins --scope local
# RESTART Claude Code after installing (required!)
Once installed, start a session with the main agent:
claude --agent epa-programmer-main-agent
Development Only (--plugin-dir)
--plugin-dir loads a plugin directly from a local directory without marketplace installation. Use only during plugin development.
claude --plugin-dir ./OUTPUT_SKILLS/emasoft-programmer-agent
Requirements
SERENA MCP (REQUIRED)
The Programmer Agent relies on SERENA MCP for code investigation:
- Symbol search
- Function/class lookup
- Call graph analysis
- Import/dependency tracking
SERENA must be available before starting work.
Supported Languages
| Language | Toolchain | Linter | Formatter | Type Checker |
|---|
| Python | uv | ruff check | ruff format | mypy |
| JavaScript/TypeScript | bun | eslint | prettier | tsc |
| Rust | cargo | clippy | rustfmt | Built-in |
| Go | go | golint | gofmt | Built-in |
| .NET (C#/F#) | dotnet | Built-in | Built-in | Built-in |
| C/C++ | gcc/clang | clang-tidy | clang-format | Built-in |
| Objective-C | clang | clang-tidy | clang-format | Built-in |
| Swift | swift | swiftlint | swift-format | Built-in |
Troubleshooting
Plugin Not Loading
Symptom: Commands/agents not available after installation
Cause: Claude Code caches plugin metadata
Solution: Restart Claude Code after installation/updates
SERENA MCP Not Available
Symptom: Code investigation fails with "SERENA not available"
Cause: SERENA MCP server not configured or not running
Solution:
- Verify SERENA MCP is configured in Claude Code settings
- Check MCP server is running:
curl http://localhost:PORT/health
- Restart Claude Code to reconnect to MCP servers
Tests Not Running
Symptom: Tests fail with "command not found"
Cause: Language toolchain not installed or not in PATH
Solution:
- Install required toolchain (see Supported Languages table)
- Verify toolchain is in PATH:
which uv / which bun / etc.
- Restart terminal/Claude Code to pick up PATH changes
Code Fixer Agent Failing
Emasoft
