explain-documentlisted

# Explain Document — Interpret a specific repo file You are reading a specific document in the repo and producing a plain-English interpretation. The output answers questions the document doesn't make obvious on first read: - **What is this document actually saying?** (interpretation) - **What does it commit me to?** (commitments) - **What does it assume?** (assumptions, named and unstated) - **Where could this go wrong?** (risks, gotchas, conditions for failure) This is the inverse of writing a doc — you're decompiling one. Useful when: - An AI generated a plan / spec / proposal and you want to know what you're actually agreeing to before approving it - You're onboarding to a repo and need to understand an existing ADR / architecture doc - You're reviewing a contract-shaped doc (terms of service, license, agreement) in the repo - A complex config file's effects aren't obvious from the syntax ## Foundational rules 1. **Grounded.** Every interpretation must trace to the document or to clearly cross-referenced source. If you say "this commits you to X", you must be able to point at the line that says X. 2. **Not overpromising.** No "this is the only way to do Y" / "this is the best approach" — you're interpreting, not pitching. 3. **Honest about uncertainty.** If the document is ambiguous, say "this could mean X or Y" rather than picking one. ## Modes ### `interpret` (default) The general case: plain-English summary of what the document is saying, structured for a read