Yes. The Java/Spring Boot source content is already in ECC, but the Kiro-facing adapter has not been mirrored for that lane yet.

Current ECC source paths:

• agents/java-reviewer.md
• agents/java-build-resolver.md
• rules/java/
• skills/springboot-patterns/
• skills/springboot-security/
• skills/springboot-tdd/
• skills/springboot-verification/

For now, the practical path is to copy those into the Kiro surface using the same shape as the existing .kiro/agents/go-reviewer.* files:

mkdir -p .kiro/agents .kiro/skills .kiro/steering/java
cp agents/java-reviewer.md .kiro/agents/java-reviewer.md
cp agents/java-build-resolver.md .kiro/agents/java-build-resolver.md
cp -R rules/java/* .kiro/steering/java/
cp -R skills/springboot-* .kiro/skills/

The missing durable piece is generating the .kiro/agents/java-reviewer.json and .kiro/agents/java-build-resolver.json descriptors, then adding that to the install/package validation path so Kiro users get Java/Spring Boot without manual copying.

So the answer is: yes, bring it from ECC's Java/Spring Boot agents, rules, and skills into .kiro/; the repo still needs a follow-up Kiro adapter PR to make this first-class.