cavecrew

Identify when to delegate debugging tasks to compressed subagent outputs.

1|Updated Jun 22, 2026
One-click install
npx skills add https://github.com/jchildree/The-QUESTION --skill cavecrew-jchildree
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: cavecrew
Source: https://github.com/jchildree/The-QUESTION/tree/main/.agents/skills/cavecrew
Command: npx skills add https://github.com/jchildree/The-QUESTION --skill cavecrew-jchildree

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

The Cavecrew skill unit solves the problem of information overload during complex debugging sessions by suggesting the use of compressed, subagent-driven output when it is appropriate.

Core Features & Use Cases

  • Selective Subagent Use: Helps determine when to delegate tasks to caveman-style subagents like cavecrew-investigator, cavecrew-builder, and cavecrew-reviewer.
  • Context Conservation: Subagents' outputs are more concise, helping maintain the context over long debugging sessions.
  • Use Case: During a bug investigation, instead of receiving lengthy responses from Explore or Code Reviewer, use Cavecrew to get compact findings that can be acted upon more efficiently.

Quick Start

To determine whether to use cavecrew, consider phrases like "delegate to subagent" or "use cavecrew".

Frequently Asked Questions about cavecrew

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I preserve main thread context during long debugging sessions?

To preserve main thread context during long debugging sessions, delegate information retrieval and investigation tasks to compressed subagent outputs. This prevents information overload by returning concise findings instead of lengthy responses.

What is compressed subagent output and when should I use it?

Compressed subagent output is a concise format returned by delegated subagents during code investigation. Use it during prolonged bug investigations when lengthy responses from standard tools would overwhelm your available context window.

How do I delegate tasks to subagents for more concise code review findings?

Delegate tasks to subagents by invoking specialized roles like investigator, builder, or reviewer. These subagents process code review requests and return compact findings that can be acted upon more efficiently than full-length outputs.

Does using subagent-driven output work for large-scale bug investigations?

Subagent-driven output is suitable for large-scale bug investigations requiring long-term context conservation. It selectively delegates information retrieval to maintain efficiency, making it ideal for environments needing concise task delegation over extended periods.

What are the limitations of using compressed subagent output for information retrieval?

Compressed subagent output is limited to scenarios requiring concise information retrieval and task delegation. It should not be used when full-length, detailed responses from standard exploration or code review tools are necessary for the investigation.

Why does context conservation matter when debugging complex software issues?

Context conservation matters when debugging complex software because lengthy automated responses cause information overload. By selectively using compressed subagent output, you maintain available context and improve efficiency throughout prolonged investigation sessions.