cavecrew

Guides delegation to compressed-output subagents for code location, editing, and review tasks.

Updated May 8, 2026
One-click install
npx skills add https://github.com/tomw200082-collab/gt-factory-os-production-brain --skill cavecrew-tomw200082-collab
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: cavecrew
Source: https://github.com/tomw200082-collab/gt-factory-os-production-brain/tree/main/.claude/skills/cavecrew
Command: npx skills add https://github.com/tomw200082-collab/gt-factory-os-production-brain --skill cavecrew-tomw200082-collab

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Long coding sessions exhaust the main context window because vanilla subagent results are injected back verbatim as verbose prose. This Skill tells you when to delegate to caveman-compressed subagents so each delegation costs roughly one third the tokens. ## Core Features & Use Cases - Decision matrix: Maps task types (locate code, surgical edit, diff review) to the right subagent — cavecrew-investigator, cavecrew-builder, or cavecrew-reviewer — versus vanilla agents or the main thread. - Output contracts: Defines exact structured formats each subagent returns (path:line findings, change confirmations, severity-tagged review findings) so results are greppable and predictable. - Chaining patterns: Documents locate → fix → verify workflows, parallel investigator scouting, and single-shot edits. - Use Case: During a long refactoring session, spawn cavecrew-investigator to find all call sites of a function, hand the top two paths to cavecrew-builder for the edit, then have cavecrew-reviewer audit the diff — all while keeping main-context usage minimal. ## Quick Start Ask the assistant to delegate code exploration to a cavecrew investigator subagent to save context, for example by saying "use cavecrew to find where this function is defined".

Frequently Asked Questions about cavecrew

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

FAQPage Schema
How do I delegate code search to a subagent in Claude Code?▼

Use cavecrew-investigator for read-only code location tasks like finding definitions, callers, or usages. It returns compressed path:line findings instead of prose, keeping the result injected into main context small.

When should I use a subagent instead of editing code directly?▼

Delegate when the task is a surgical edit of one to two files with obvious scope, or a read-only search. Keep one-line answers and three-plus-file refactors on the main thread, since builder subagents refuse oversized scope.

Cavecrew vs vanilla Explore agent: which should I use?▼

Use cavecrew-investigator when you want terse path:line findings at roughly one third the token cost. Use vanilla Explore when you want prose, architecture commentary, or rationale alongside the locations.

Can I change the model a Claude Code subagent uses?▼

Yes. Set CAVECREW_REVIEWER_MODEL, CAVECREW_BUILDER_MODEL, or CAVECREW_INVESTIGATOR_MODEL environment variables before launching Claude Code to override the pinned model in each agent's frontmatter.

What are the limitations of compressed subagent output?▼

Caveman output is structured and terse, sometimes cryptic for direct human reading, and reviewers return findings only without architecture opinions. For deep reviews with rationale, use a vanilla Code Reviewer agent instead.