caveman--cavecrew

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

Updated Dec 3, 2025
One-click install
npx skills add https://github.com/hhenrichsen/dots --skill caveman-cavecrew-hhenrichsen
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: caveman--cavecrew
Source: https://github.com/hhenrichsen/dots/tree/main/dot_skills/caveman/cavecrew
Command: npx skills add https://github.com/hhenrichsen/dots --skill caveman-cavecrew-hhenrichsen

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Subagent tool results are injected verbatim into the main conversation context, so verbose agent output quickly exhausts the context budget during long sessions. This Skill provides a decision guide for when to delegate work to three compressed-output subagents instead of working inline or using default agents. ## 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. - Output Contracts: Defines compact, greppable return formats (path:line findings, severity-tagged review findings) so results consume fewer main-context tokens. - Chaining Patterns: Documents workflows like locate → fix → verify and parallel scouting with multiple investigators. - Use Case: During a long debugging session, spawn cavecrew-investigator to find all callers of a function, hand the best site to cavecrew-builder for a two-file fix, then have cavecrew-reviewer audit the diff — all while keeping main context lean. ## Quick Start Ask the assistant to delegate code investigation to a cavecrew subagent instead of exploring inline when you want compressed results.

Frequently Asked Questions about caveman--cavecrew

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

FAQPage Schema
When should I delegate to a subagent instead of working inline?▼

Delegate when the subagent's output can be compressed to roughly a third of the tokens of prose output. Work inline for one-line answers you already know and for refactors spanning three or more files.

What is the difference between cavecrew-investigator and the Explore agent?▼

cavecrew-investigator returns compact path:line findings with backticked symbols, while Explore returns prose with architecture commentary. Choose the investigator for locate-only questions and Explore when you want suggestions and rationale.

Can cavecrew-builder handle multi-file refactors?▼

No. cavecrew-builder only accepts surgical edits of one to two files with obvious scope and returns 'too-big.' for larger requests. Use the main thread or a code-architect agent for three-plus file changes.

How do I override the model used by cavecrew subagents?▼

Set environment variables before launching Claude Code: CAVECREW_REVIEWER_MODEL, CAVECREW_BUILDER_MODEL, or CAVECREW_INVESTIGATOR_MODEL with values like haiku, sonnet, or opus. Overrides patch only the model line in installed agent frontmatter.

Why does cavecrew output look terse or cryptic?▼

Cavecrew agents emit structured, compressed output by design to reduce main-context token usage. If a human will read the result directly, paraphrase it into normal prose first.