brieflisted

# /brief — Project-Aware Session Briefing Build a synthesized briefing of the project so Claude knows what the project IS, how it works, and what to avoid before doing anything else. ## Optional delegation mode If the project has `.claude/llm-mode.json` and its `mode` is `"multi"`, delegate the heavy doc reading to a cheaper CLI (Antigravity CLI — `agy`, previously the Gemini CLI — is a common pick). Only pull the result back to synthesize. If the file is absent or mode is `"single"`, run the standard path. If the delegated call fails, fall back to standard silently. Example delegated call: ```bash # `agy` (Antigravity CLI) replaces the sunset Gemini CLI on consumer plans as of # 2026-06-18; enterprise plans may still use the legacy `gemini` binary. The model # identifier (`gemini-3-pro`) is unchanged. # # Note: piping into `agy` already provides stdin, so the `</dev/null` gotcha that # applies to bare `agy -p "..."` doesn't bite here. For non-piped scripted calls # elsewhere, always write `agy -p "<prompt>" </dev/null`. echo "You are a research analyst. I am about to work on: $TASK. Review the attached documentation and output a Pre-Task Briefing: 1. WATCH OUT — past mistakes, forbidden patterns, known issues 2. HARD CONSTRAINTS — non-negotiable rules 3. PROJECT CONTEXT — what this project IS, tech stack, capabilities 4. STRATEGIC CONTEXT — goals, audience, positioning 5. RELATED WORK — existing content, features, or code that overlaps 6. RECOMMENDATIONS — specific sug