Register specialized agents so they are used and repair option #4

New Issue

tegwick · 2025-10-27T15:57:12Z

tegwick commented

2025-10-27 15:57:12 +00:00

Seeding specialized agents into a repository should enable the main coding agent to know about the specialized agents and be able to delegate or suggest to delegate tasks to the correct subagent.

There should be an idempotent register command that does this. Check the current "install" command and delegate the integration part to a register function. My hunch is init should do install and register agents.

I am currently working with claude code and integrating subagents and tools is claude code specific. Also best practices are evolving to do this. As a consequence lets have a plugin infrastructure to support different coding environments and the specific versions of coding agents utilized.

The kaizen-agent repair command should be provided to:

validate the agents installed
reregister the agents to fix what might have generated since the last registration
update the agents installed
register the updated agents
validate the agents again

Here is some input for how to achieve the registration of agents with claude code from an earlier conversation:

Agent Registration Fix Plan

Problem: The keepaChangelog agent exists but isn't available in Claude Code's Task tool because
there's no integration between the project's AgentRegistry and the Task tool's hardcoded agent
types.

Solution: Create a bridge mechanism to make project-specific agents available to the Task tool.

Implementation Steps

Create Agent Bridge Script (tools/register_agents.py)

Load agents from /agents/ directory using existing AgentRegistry
Generate a configuration file that maps agent names to their definitions
Include agent instructions and metadata for Task tool consumption

Update Claude Code Configuration (.claude/settings.local.json)

Add project-specific agent definitions to make them available as subagent_type options
Map changelog-keeper to keepaChangelog for the Task tool
Register all 17 available agents from the agents directory

Test Agent Availability

Verify keepaChangelog appears as available subagent_type
Confirm agent can be invoked via Task tool
Test with changelog update task

Expected Outcome

All 17 specialized agents become available as subagent_type options
keepaChangelog (mapped from changelog-keeper) can be used for changelog maintenance
Future agents added to /agents/ automatically become available

Files to Modify

Create: tools/register_agents.py
Update: .claude/settings.local.json

This approach leverages the existing AgentRegistry infrastructure and creates a minimal bridge to
Claude Code's agent system.

Seeding specialized agents into a repository should enable the main coding agent to know about the specialized agents and be able to delegate or suggest to delegate tasks to the correct subagent. There should be an idempotent register command that does this. Check the current "install" command and delegate the integration part to a register function. My hunch is init should do install and register agents. I am currently working with claude code and integrating subagents and tools is claude code specific. Also best practices are evolving to do this. As a consequence lets have a plugin infrastructure to support different coding environments and the specific versions of coding agents utilized. The kaizen-agent repair command should be provided to: - validate the agents installed - reregister the agents to fix what might have generated since the last registration - update the agents installed - register the updated agents - validate the agents again Here is some input for how to achieve the registration of agents with claude code from an earlier conversation: Agent Registration Fix Plan Problem: The keepaChangelog agent exists but isn't available in Claude Code's Task tool because there's no integration between the project's AgentRegistry and the Task tool's hardcoded agent types. Solution: Create a bridge mechanism to make project-specific agents available to the Task tool. Implementation Steps 1. Create Agent Bridge Script (tools/register_agents.py) - Load agents from /agents/ directory using existing AgentRegistry - Generate a configuration file that maps agent names to their definitions - Include agent instructions and metadata for Task tool consumption 2. Update Claude Code Configuration (.claude/settings.local.json) - Add project-specific agent definitions to make them available as subagent_type options - Map changelog-keeper to keepaChangelog for the Task tool - Register all 17 available agents from the agents directory 3. Test Agent Availability - Verify keepaChangelog appears as available subagent_type - Confirm agent can be invoked via Task tool - Test with changelog update task Expected Outcome - All 17 specialized agents become available as subagent_type options - keepaChangelog (mapped from changelog-keeper) can be used for changelog maintenance - Future agents added to /agents/ automatically become available Files to Modify - Create: tools/register_agents.py - Update: .claude/settings.local.json This approach leverages the existing AgentRegistry infrastructure and creates a minimal bridge to Claude Code's agent system.

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: coulomb/kaizen-agentic#4