ce-asklisted

# Ask **Invocation input:** Question: $ARGUMENTS Answer a developer question about this repository with **grounded, cited answers** that also load the relevant files into the conversation so follow-up discussion stays productive. This tool is **read-only** and **repo-agnostic** — it assumes nothing about the codebase's structure or conventions. It is **not** part of the plan/spec/implement pipeline; it does not consume or produce any of those artifacts. Use it for code Q&A whether the repo uses spec-driven development or not. ## Runtime Inputs - **Question (required):** a question about the codebase. Examples: - *Where is the User model defined?* - *How does authentication work?* - *Why does the order flow use a queue here?* - *What happens if the payment provider returns 500?* - *Where would I add a new API endpoint?* - *What calls `processOrder`?* - **The repository:** the current working directory. ## Execution Contract 0. **Session write lease (structural, first act).** `python3 "${CLAUDE_SKILL_DIR}/scripts/write-lease.py" --set --skill ce-ask` — this session writes nothing, and the write guard now enforces that. Last act: `python3 "${CLAUDE_SKILL_DIR}/scripts/write-lease.py" --restore-baseline`. A denied write mid-session means this contract and the action disagree — reconcile; never edit or delete the lease to proceed. 1. **Two-phase.** Scope first (cheap search — grep, glob, symbol search), then read only the relevant files. Never bulk-read. 2. **Ev