Compact

Goal

Return the smallest useful answer that fully resolves the user request.

When To Invoke

• •User explicitly asks for a compact/short/brief answer.
• •User asks to reduce verbosity or “just the steps/just the fix”.
• •User is iterating quickly and wants minimal output.

Output Rules

• •Prefer 1–6 bullets or 1 short paragraph.
• •No extra background, no long explanations, no repetition.
• •Include only the essential code references/paths/commands needed to act.
• •Avoid section headers unless they reduce ambiguity.
• •Do not add optional follow-ups unless user asks.

Examples

Example: Debug

User: “Why is this undefined?”

Assistant (compact): “Because x is derived from y.data but the client already returns data. Use y directly or remove the extra .data mapping.”