Orchestrator Agent with Parallel Sub-Agents in Kiro CLI

Figure 1. kiro orchestrator agents Overview Kiro CLI allows us to configure an orchestrator agent that executes specialized sub-agents in parallel. Each sub-agent has its own tools, permissions, and MCP servers – the parent’s trust settings are not inherited. Architecture Figure 2. Agents flow Step 1: Define Specialized Agents We give each sub-agent its own JSON configuration under .kiro/agents/. .kiro/agents/code-agent.json { "name": "code-agent", "description": "Implements features and writes code", "prompt": "You are an experienced Kotlin/Java developer. Write clean, tested code.", "tools": ["read", "write", "shell", "code", "grep"], "allowedTools": ["read", "code", "grep"], "toolsSettings": { "write": { "allowedPaths": ["./src/**", "./tests/**"], "deniedPaths": ["./.env", "./secrets/**"] }, "shell": { "allowedCommands": ["mvn test", "mvn compile"], "autoAllowReadonly": true } } } ...

July 2, 2026 · 4 min · 784 words · Micha Kops

Dependency management in Grails 1.2

Sometimes I get the impression that there are many Maven haters in the Groovy/Grails community – now with version 1.2 of the Grails framework they are able to abandon the evil satanic Grails Maven Plugin and embrace the neverending joys of a slim, nice, sexy dependency resolution dsl .. here we go .. lets define some dependencies wheee … Our dependency configuration is defined in grails-app/config/BuildConfig.groovy as a property named grails.project.dependency.resolution: grails.project.dependency.resolution = { // here will be some dependencies } ...

May 23, 2010 · 2 min · 336 words · Micha Kops

Manage dependencies with the Maven Dependency Plugin

In a maven project there are lots of dependencies to handle – often one wants to know which version of a software comes from. The solution to this problem is the Maven Dependency Plugin which helps you to find used/unused/declared/undeclared dependencies in your project. In addition the plugin allows you to copy or unpack artifacts. Maven Goals dependency:copy – copies artifacts defined in the config to a specified location – details available here dependency:resolve – resolves all dependencies and shows the versions dependency:go-offline – resolves everything the project needs like dependencies, plugins and reports dependency:analyze - parses the dependencies and shows if they are used/declared/unused/undeclared .. dependency:analyze-dep-gmt - finds mismatches between resolved dependencies and those listed in the dependencyManagement section dependency:tree – shows a nice dependency tree for the maven project ...

April 4, 2010 · 2 min · 321 words · Micha Kops