Apply R&D framework to optimize prompts and context. Use when optimizing context window usage, reducing prompt size, delegating to specialized agents, or applying systematic context management.
Applies the Reduce & Delegate framework to optimize context usage. Use when context is bloated, prompts are unwieldy, or you need to offload work to specialized agents.
/plugin marketplace add melodic-software/claude-code-plugins/plugin install google-ecosystem@melodic-softwareThis skill is limited to using the following tools:
Apply the R&D framework to optimize prompts, workflows, and context management.
There are only two ways to manage context: Reduce and Delegate. This skill helps you systematically apply both strategies to any context optimization challenge.
Categorize the issue:
| Problem Type | Indicator | Primary Strategy |
|---|---|---|
| Context Rot | Old info guiding decisions | Reduce (fresh instance) |
| Context Pollution | Unfocused, tangential | Reduce (remove irrelevant) |
| Toxic Context | Contradictory behavior | Reduce (clear conflicts) |
| Context Overflow | Approaching limits | Delegate (offload work) |
For each context element, ask:
Reduction techniques:
| Technique | Application |
|---|---|
| Fresh instance | New task type, reset history |
| Output styles | Control verbosity, reduce tokens |
| Focused reads | Specific files vs directories |
| Priming commands | Replace static memory |
| MCP cleanup | Remove unused servers |
For complex or parallel work, ask:
Delegation techniques:
| Technique | Application |
|---|---|
| Sub-agents | Focused tasks with isolated context |
| Background agents | Parallel work, async execution |
| Agent experts | Domain-specific knowledge |
| Spec files | Handoff between agents |
1. Measure current context state
- Use /context command
- Check token consumption
2. Analyze composition
- What's consuming most tokens?
- What's unnecessary?
3. Apply Reduce
- Remove unnecessary context
- Start fresh if needed
- Control output verbosity
4. Apply Delegate
- Offload subtasks
- Use specialized agents
- Enable parallel work
5. Verify improvement
- Measure new state
- Compare performance
Before:
# CLAUDE.md (5KB+)
Contains: everything about the project
After (Reduce):
# CLAUDE.md (1KB)
Contains: only universals
# .claude/commands/prime.md
Contains: task-specific context loading
Problem: Multi-turn conversation with context rot
Solution (Reduce):
Before:
Primary agent does research -> context polluted
Primary agent implements -> struggles with focus
After (Delegate):
Primary agent delegates research -> sub-agent
Sub-agent returns summary -> primary continues
Primary agent implements -> clean context
Before:
Task A -> Task B -> Task C (sequential, context accumulates)
After (Delegate):
Task A (agent 1) \
Task B (agent 2) -> Aggregate results
Task C (agent 3) /
When optimizing, report:
{
"analysis": {
"current_state": "Context at 80% capacity",
"primary_issue": "Long conversation with accumulated history",
"secondary_issues": ["Verbose tool outputs", "Unused MCP servers"]
},
"reduce_recommendations": [
{
"action": "Start fresh instance",
"impact": "Reset accumulated history",
"effort": "Low"
},
{
"action": "Apply concise output style",
"impact": "50% reduction in output tokens",
"effort": "Low"
}
],
"delegate_recommendations": [
{
"action": "Create research sub-agent",
"impact": "Isolate research context",
"effort": "Medium"
}
],
"expected_improvement": "40-60% context reduction"
}
When to Reduce vs Delegate:
| Situation | Reduce | Delegate |
|---|---|---|
| Stale context | X | |
| Irrelevant context | X | |
| Conflicting context | X | |
| Complex subtask | X | |
| Parallel work | X | |
| Domain expertise needed | X | |
| Context overflow | X | X |
"There are only two ways to manage your context window: Reduce and Delegate. Every technique fits into one or both of these buckets."
Date: 2025-12-26 Model: claude-opus-4-5-20251101
This skill should be used when the user asks to "create a slash command", "add a command", "write a custom command", "define command arguments", "use command frontmatter", "organize commands", "create command with file references", "interactive command", "use AskUserQuestion in command", or needs guidance on slash command structure, YAML frontmatter fields, dynamic arguments, bash execution in commands, user interaction patterns, or command development best practices for Claude Code.
This skill should be used when the user asks to "create an agent", "add an agent", "write a subagent", "agent frontmatter", "when to use description", "agent examples", "agent tools", "agent colors", "autonomous agent", or needs guidance on agent structure, system prompts, triggering conditions, or agent development best practices for Claude Code plugins.
This skill should be used when the user asks to "create a hook", "add a PreToolUse/PostToolUse/Stop hook", "validate tool use", "implement prompt-based hooks", "use ${CLAUDE_PLUGIN_ROOT}", "set up event-driven automation", "block dangerous commands", or mentions hook events (PreToolUse, PostToolUse, Stop, SubagentStop, SessionStart, SessionEnd, UserPromptSubmit, PreCompact, Notification). Provides comprehensive guidance for creating and implementing Claude Code plugin hooks with focus on advanced prompt-based hooks API.