If you want to use the Agents for Java definitions shipped with this repository, read this document. It covers the curated agents under .cursor/agents used for Java Enterprise delivery workflows (excluding the diagramming specialist; see note below).
In Cursor, an agent is a reusable persona defined as a Markdown file with YAML frontmatter (name, model, description, and optional flags such as readonly). Cursor loads these files from .cursor/agents/. Each agent file spells out role, responsibilities, constraints, and which Skills or rules to apply—so the model behaves consistently for that kind of task.
- Requirements quality: robot-business-analyst is read-only: it reviews user stories, plans, and ADRs for alignment, gaps, and traceability—useful before sign-off or when documents disagree.
- Orchestration: robot-coordinator reads implementation plans (especially tables with a Parallel column), identifies the stack (Spring Boot, Quarkus, Micronaut, or plain Java), and delegates work to exactly one implementation agent for the engagement. It does not implement code itself.
- Implementation (delegation only): robot-java-coder, robot-spring-boot-coder, robot-quarkus-coder, and robot-micronaut-coder are the specialists the coordinator delegates to. You should not
@-mention them directly for plan-driven implementation—start with @robot-coordinator so it picks the right stack and hands off work (including Parallel groups). They reference the Skills for Java catalog (for example@301–@323for Spring Boot) when relevant.
Note: The repository may include other agent definitions in .cursor/agents (for example architecture or diagramming specialists). This guide covers only the Java delivery and BA agents listed below.
Agents assume you can attach Skills (see Getting started for Skills for Java) and/or Cursor rules (see Getting started for System prompts for Java) so that @… references resolve in chat. The implementation agents name concrete skill prefixes (for example @322-frameworks-spring-boot-testing-integration-tests).
Agents live next to your other Cursor project config. Install them the same way you install Cursor rules: copy the whole .cursor directory into the root of your Java repository (or use the same workflow you already use for .cursor/rules).
- From a Git clone or ZIP: Copy the folder
.cursor/agents(or the entire.cursortree) into your project. - JBang setup (rules + Cursor layout): If you use the setup described in Getting started for System prompts for Java, ensure your process also preserves or copies
.cursor/agentswhen you sync from this repository.
After installation you should see files such as robot-coordinator.md under .cursor/agents/ in your project.
For implementation from a plan, your entry point is @robot-coordinator only. It identifies the stack and delegates to the correct robot-*-coder; do not @-mention the coder agents yourself for that workflow.
| Agent | Role | How you use it |
|---|---|---|
| robot-business-analyst | BA review: stories ↔ plan ↔ ADRs; readonly. | @ this agent directly for requirements review (not part of the coordinator’s implementation delegation). |
| robot-coordinator | Coordinates work from *.plan.md; routes to one framework-specific implementer; splits handoffs by Parallel group. |
@ this agent when you have a structured plan (with Parallel / execution order when applicable) and want implementation delegated in order. |
| robot-java-coder | Plain Java / Maven implementation specialist. | Delegation target only—the coordinator assigns this agent when the stack is plain Java or framework-neutral. |
| robot-spring-boot-coder | Spring Boot implementation (REST, Data JDBC, test slices, etc.). | Delegation target only—the coordinator assigns this agent when the stack is Spring Boot. |
| robot-quarkus-coder | Quarkus implementation (Jakarta REST, CDI, Panache/JDBC, Quarkus tests). | Delegation target only—the coordinator assigns this agent when the stack is Quarkus. |
| robot-micronaut-coder | Micronaut implementation (@Controller, Micronaut Data, HttpClient tests). |
Delegation target only—the coordinator assigns this agent when the stack is Micronaut. |
- Open your Java repository that already has
.cursor/agents(and preferably Skills / rules as above). - For implementation, mention only @robot-coordinator and attach the plan; describe milestones or constraints in the message. The coordinator’s job is to delegate to the right
robot-*-coder(you do not@those coders yourself for plan execution). - For requirements review, mention @robot-business-analyst directly and attach or paste stories, plans, and ADRs.
Examples:
- “Using @robot-coordinator, execute the plan at
path/to/PLAN-*.plan.mdand delegate implementation per Parallel groups.” - “Using @robot-business-analyst, review these files for traceability: [paste or attach stories, plan, ADRs].”