ground-claim

## Trigger **Mode: capability** (default) — Self-referential meta-capability questions about the current repository, framework, or system: - "What does this repo enable?" - "What are the orchestration patterns available?" - "List the available skills." - "What capabilities does the plugin provide?" **Mode: runtime-wiring** — Claims that require tracing actual execution paths, not static structure: - "Verify that middleware Y intercepts all requests." - "Confirm plugin Z is loaded on startup." - "Validate that feature X is active in production." Skip both modes for: usage questions ("how do I use X?"), bug reports, feature requests. --- ## Mode: capability (default) ### Procedure 1. **Extract capability nouns.** From the user's question, identify 2–5 concrete capability categories (e.g., skills, hooks, agents, orchestration patterns, CLI commands, verification methods). Write them down. 2. **Locate and read evidence.** For each capability noun: - Use Glob or Grep to locate source files (e.g., `skills/*/SKILL.md` for skills, `hooks/` for hooks, `agents/` for agents). - Read at least one concrete source file per capability. Record the file path and specific line numbers. - Do not rely on training data, model recall, or session-listing attachments. Evidence must come from Read tool output. 3. **Build the answer inline.** Embed citations **within claims**, not in a separate appendix. Format: `path/to/file.md:line—<claim context>`. 4. **Tag ungrounded claims.** I...