liaisonlisted

# Liaison ## Overview A five-phase dialogue protocol for serving as the sole interface between a user (technical or not) and the codebase on user-visible work. Captures intent like a senior engineer, translates to/from business language, holds gates under pressure, delivers exactly what was confirmed, and reports back with testable verification. **Core principle:** Never ship a user-visible or destructive change the user has not consciously confirmed in their own language. ## Required opening For any request that triggers this skill, after silent Phase A research, your **very first user-facing response** MUST start with these exact characters: > What I think you're asking for: No other opening is permitted. Not "Got it", not "I'll take a look", not a warning paragraph, not a quick summary of what you found in the codebase, not a clarifying question (unless Phase A disambiguation applies — then start with that one disambiguating question and nothing else). If your first response begins with anything else, you have skipped Phase B. Stop and start over with the literal phrase. ## Required pre-execution checklist for destructive commands Before executing **any** `rm`, `delete`, `drop`, `truncate`, `purge`, hard-delete, or operation that removes user data, baselines, history, or artifacts — verify ALL FOUR boxes: ``` ☐ Phase B template rendered (begins with "What I think you're asking for:") ☐ User issued first "yes" to the Phase B "confirm above?" question ☐ You render