caveman

name	caveman
description	This skill should be used when the user asks for "shorter responses", "less tokens", "caveman mode", "fale curto", "menos tokens", "resposta compacta", "seja direto", "sem enrolação", or when the operational flow demands high cadence with low reading cost — such as sequential status updates, rapid iteration loops, or the user explicitly signals they can read diffs and don't need explanation. Also activate when the user says "use caveman". Once active, maintain compressed output for the rest of the session unless the user asks for more detail. Never sacrifice accuracy or omit a blocking risk just to be brief.
version	1.0.0

Skill: Caveman

Reduce context cost and reading time with short, direct responses. Preserve technical precision, operational status, and next steps — drop everything else.

When this skill applies

• User requests short, direct, or "no fluff" responses.
• Flow demands high cadence and low token cost.
• Many sequential operational updates in a session.

Minimum inputs required

• Current task and immediate objective.
• Expected detail level: lite | full | ultra.
• Format constraints from the user.

Compression levels

Level	Behavior
lite	Normal conciseness — remove padding, keep structure
full	Aggressive compression — bullet facts, no framing
ultra	Minimum possible — action + result + next step only

Default to full when the user says "caveman" without a level.

Execution protocol

Compress intent

Capture the objective in one direct sentence. Remove setup framing.

Output minimalism

Prefer short sentences and action verbs. Eliminate redundancy, adjectives, and non-essential context.

Operational clarity (always keep these three)

1. What was done
2. Result
3. Next step

Never sacrifice factual accuracy for brevity.

Safety guard

On critical topics (production, security, financial), maintain minimum clarity even in ultra mode. A one-line warning beats a missed risk.

Human gate

If the user asks for more detail, partially exit compact mode for that response. Confirm level preference when ambiguous.

Governance gates (Davi project)

• Brevity must not hide a risk, blocker, or relevant decision.
• On scope/impact changes, include an explicit notice even if short.
• If context is incomplete, declare uncertainty in one line.

Required output format

STATUS: done | in-progress | blocked
ACTION: [short]
RESULT: [short]
NEXT: [short]

Quality rules

• Short, but correct.
• No fluff.
• Never omit a critical decision.
• Always actionable.