Getting Started with Agents for Java
July 13, 2026 ยท View on GitHub
The embedded agents separate analysis, architecture, technical leadership, and implementation. Install them with @005-agents-installation; the canonical definitions live under plinth-skills-generator/src/main/resources/skill-references/assets/agents/.
Agent Missions
| Agent | Missions | Usage |
|---|---|---|
robot-business-analyst | Refine GitHub/Jira issues. Perform read-only alignment, traceability, and readiness reviews. | Use /update-issue or /review-alignment. It does not implement code or silently correct artifacts. |
robot-architect | Explore design alternatives. Create ADRs. Create architecture diagrams. | Use /explore-design, /create-adr, or /create-diagram. It hands approved constraints to the tech lead. |
robot-tech-lead | Create OpenSpec changes. Coordinate delivery. Select and delegate to implementation agents. Track implementation and verification. | Use /create-spec, or provide an approved plan/OpenSpec task list for delivery. |
robot-java-performance | Coordinate profiling and benchmarking. Preserve baseline and measurement evidence. Delegate approved optimizations to coder agents. | Use /profile or /benchmark. It does not implement application code directly. |
robot-java-coder | Implement framework-neutral Java and Maven work. | Delegation target selected by the tech lead. |
robot-java-spring-boot-coder | Implement Spring Boot work. | Delegation target selected by the tech lead. |
robot-java-quarkus-coder | Implement Quarkus work. | Delegation target selected by the tech lead. |
robot-java-micronaut-coder | Implement Micronaut work. | Delegation target selected by the tech lead. |
The business analyst, architect, tech lead, and Java performance agent do not replace coder agents. The tech lead selects one implementation agent from repository evidence and delegates parallel groups only when dependencies and file ownership permit it. The Java performance agent delegates approved optimizations to the appropriate coder after profiling or benchmark evidence is available.
Migration
robot-coordinator was renamed to robot-tech-lead. There is no compatibility alias. After reinstalling the bundle:
- Replace direct
@robot-coordinatormentions with@robot-tech-lead. - Replace references to
robot-coordinator.mdwithrobot-tech-lead.md. - Keep the existing delegation model: coder agents remain implementation targets.
Examples
Using @robot-business-analyst, create a GitHub issue from these requirements.Using @robot-architect, explore design alternatives for issue #806.Using @robot-tech-lead, create an OpenSpec change directly from this approved issue.Using @robot-tech-lead, deliver the selected OpenSpec tasks and delegate each implementation group.
See Project Workflows for lifecycle paths and artifact authority.