Receives via prompt:
Runs focused improvement on plugin analysis by launching specialized optimizers for context, orchestration, or handoff patterns. Filters files by focus area to reduce context duplication, then aggregates improvements into state. Use after analysis phase to address specific architectural issues.
/plugin marketplace add abossenbroek/abossenbroek-claude-plugins/plugin install context-engineering@abossenbroek-claude-pluginsReceives via prompt:
analysis_id: Session ID from analyze phasefocus_area: context|orchestration|handoff|allNOT PROVIDED (context isolation):
Read Analysis from State
python scripts/state_manager.py read "$plugin_path" --field mutable
Extract analysis_summary for selective context.
Filter File References by Focus Area
Before launching each improver, filter file_refs to pass only relevant files:
python scripts/file_cache.py get_refs_by_focus "$plugin_path" "$focus_area"
This reduces context duplication by ~2x by passing only files matching the focus area patterns.
Launch Improvers Based on Focus Area
If focus_area = "context":
Task: Optimize context patterns
Agent: coordinator-internal/context-optimizer.md
Prompt:
analysis_summary: [from state - violations, opportunities for context]
focus_area: context
file_refs: [filtered by "context" patterns]
If focus_area = "orchestration":
Task: Improve orchestration patterns
Agent: coordinator-internal/orchestration-improver.md
Prompt:
analysis_summary: [from state - violations, opportunities for orchestration]
focus_area: orchestration
file_refs: [filtered by "orchestration" patterns]
If focus_area = "handoff":
Task: Improve handoff patterns
Agent: coordinator-internal/handoff-improver.md
Prompt:
analysis_summary: [from state - violations, opportunities for handoff]
focus_area: handoff
file_refs: [filtered by "handoff" patterns]
If focus_area = "all": Launch ALL THREE improvers IN PARALLEL, each with focus-filtered file_refs.
Collect Improvements Aggregate improvements from all launched improvers.
Store Improvements in State
python scripts/state_manager.py update "$plugin_path" improvements "$IMPROVEMENTS_JSON"
improvements_generated:
improvement_ids:
- CTX-001
- ORCH-002
- HO-003
count: [total count]
by_priority:
HIGH: [count]
MEDIUM: [count]
LOW: [count]
mutable.analysis_summary (PluginAnalysis)mutable.improvements (list of improvements with IDs)Each improver receives ONLY files relevant to its focus area:
This reduces context duplication by ~2x compared to passing all files to all improvers.
Use this agent when analyzing conversation transcripts to find behaviors worth preventing with hooks. Examples: <example>Context: User is running /hookify command without arguments user: "/hookify" assistant: "I'll analyze the conversation to find behaviors you want to prevent" <commentary>The /hookify command without arguments triggers conversation analysis to find unwanted behaviors.</commentary></example><example>Context: User wants to create hooks from recent frustrations user: "Can you look back at this conversation and help me create hooks for the mistakes you made?" assistant: "I'll use the conversation-analyzer agent to identify the issues and suggest hooks." <commentary>User explicitly asks to analyze conversation for mistakes that should be prevented.</commentary></example>