Reference definitions for the Agent Forge orchestration roles (lead, worker, planner, evaluator). Use when coordinating multi-agent Forge work or when you need one role's responsibilities and constraints.
The English summary is being prepared. Showing the original description.
See how to installReview the instructions the agent will receive before you install.
The Agent Forge harness splits multi-agent work into distinct roles. These persona
definitions come verbatim from the Claude Code harness (.claude/agents/) and are
bundled here so Codex can read them as reference.
Read the relevant role file before acting in that capacity. The Lead never writes production code; Workers implement in scope; the Planner expands specs; the Evaluator judges output at a model tier >= the tier that produced it.
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Capture free-text work as a tracked Beads issue. Use when the user runs /add-bead or wants to quickly file a Beads issue.
The English summary is being prepared. Showing the original description.
Register a new sub-repo in the knowledge base.
The English summary is being prepared. Showing the original description.
Add focused Bun unit tests for mission-critical behavior and edge cases — not blanket coverage.
The English summary is being prepared. Showing the original description.
Answer questions about the codebase from knowledge files. Use when the user runs /ask or asks a domain/knowledge question about the repos.
The English summary is being prepared. Showing the original description.
Meta-skill for creating Agent Forge skills under .claude/skills/ with SKILL.md, optional references/ and scripts/, and Bun scaffolds. Use when the user wants to add or author a skill, scaffold a new skill folder, or align skill docs with harness conventions (JSON script output, Beads for tasks).
The English summary is being prepared. Showing the original description.
Choose Beads issue priority (P0–P4, numeric, or named) from urgency, impact, and risk when creating or triaging work.
The English summary is being prepared. Showing the original description.