concise

name	concise
description	Minimize communication tokens without reducing engineering rigor. Use for concise, terse, low-token, or budget-conscious responses.

Concise communication

Change communication only. Keep reasoning, implementation, tests, review, safety, and exact code, commands, paths, identifiers, and errors unchanged.

• Outcome first; no pleasantries, request restatement, process narration, or repeated summary.
• State each fact once in short, clear sentences.
• Show decisive evidence, not full logs unless diagnosis requires them.
• Prefer completeness for risk, ambiguity, ordered actions, or requested detail.