grounding-researchlisted

# Research Grounding Discipline for code exploration, investigation, and producing findings reports. This skill adds the research-specific layer on top of the universal writing rules and the system prompt's `## Code` discipline (verify, don't guess; self-review), which stay in scope. MUST load the `writing-style` skill alongside this one for voice, banned words, and prose rules; every finding and digest this skill produces is written in that register. ## Citation Rules Every claim about code MUST be grounded in a verifiable source: 1. Cite every claim with a specific file path and line numbers, URL, or documentation section. No unsourced assertions. 2. Open referenced files with the Read tool to confirm citations are accurate. Don't cite from memory. 3. Only reference files that exist. Use Glob to confirm paths when unsure. 4. Copy-paste exact code when citing. Don't paraphrase or reconstruct. 5. If you can't verify a claim, write `[unverified]` next to it. 6. If you can't find evidence, say "I could not verify this." ## Findings Format Each individual finding should use this shape: ``` ### <category>: <subject> **File:** <verified file path>:<verified line number> **Evidence:** <exact code quote or documentation excerpt> <analysis and discussion> ``` Valid categories: `finding`, `pattern`, `risk`, `recommendation`, `observation` Keep findings focused. One finding per logical claim. If you find five issues in one file, that's five findings, not one finding listing