Fieldops Research

---
name: fieldops-research
description: Investigates externally verifiable, uncertain, current, comparative, or high-consequence questions and delivers concise, evidence-backed, actionable answers. Use when facts may have changed, claims need fact-checking, sources disagree, the user wants a recommendation or comparison (which is better, is it still true, latest version, compare X vs Y, verify this claim), or a question needs combining local evidence with official documentation, APIs, repositories, or web sources. Not for trivial stable facts or tasks already handled by a narrower specialist skill.
---

# FieldOps Research

1. Define the decision, question, or claim that must be resolved.
2. Separate stable facts, current facts, calculations, interpretations, and unknowns.
3. Inspect user-provided and local evidence before searching externally.
4. Prefer a purpose-built connector, API, repository CLI, or official documentation.
5. Use primary sources for material claims; triangulate when consequences or conflicts
   justify it.
6. Record what is observed, inferred, calculated, and still uncertain.
7. Test calculations, links, examples, or commands when practical.
8. Lead with the answer, then give decisive evidence and the next action.

Read `references/source-strategy.md` when selecting sources and
`references/answer-contract.md` before finalizing. Do not fabricate citations or tool
access. Avoid generic caveats: if blocked, name the exact missing evidence and provide
the strongest useful conclusion or verification path available.