How to resolve the conflict between the planner subagent in this project and the original plan subagent of ClaudeCode?

[Hor1zonZzz]

As the title indicates
should I use CLAUDE.md to let model use planner agent？

[affaan-m]

good question, I'd either set it as a rule or use the default claude planner and set a rule that encompasses the same functionality as the subagent

[affaan-m]

Resolving the Planner Agent Conflict

Good question @Hor1zonZzz! This is a naming collision between:

1. Claude Code's built-in Plan subagent - used for implementation planning via EnterPlanMode
2. This plugin's planner agent - located in agents/planner.md

How It Works

Claude Code's subagent system uses namespacing for plugin agents. When you install this plugin, the agent becomes:

everything-claude-code:planner

The built-in Plan agent remains separate and is invoked via EnterPlanMode tool or when Claude determines planning is needed.

Using Both

To use the built-in Plan mode:

• Ask Claude to "plan this feature" - it will use EnterPlanMode
• Or explicitly say "use Plan Mode"

To use this plugin's planner agent:

• Reference it explicitly: "use the everything-claude-code:planner agent"
• Or invoke via Task tool with subagent_type: "everything-claude-code:planner"

Recommendation

You can also add this to your CLAUDE.md to set a preference:

## Planning Preference
When I ask to plan a feature, use the `everything-claude-code:planner` agent 
instead of the built-in Plan Mode for more comprehensive implementation planning.

Future Improvement

I'll consider renaming to ecc-planner or implementation-planner in a future release to make the distinction clearer. Would that help?

[Hor1zonZzz]

Thank you for your explanation.