19 lines
1.2 KiB
Markdown
19 lines
1.2 KiB
Markdown
---
|
|
name: facts-verification
|
|
description: Use when an answer, report, or decision depends on factual claims that need checking against current or authoritative evidence; label each claim confirmed, contradicted, inferred, or unknown.
|
|
---
|
|
|
|
# Facts Verification
|
|
|
|
Use when an answer, report, or implementation decision depends on claims that need confirmation.
|
|
|
|
## Workflow
|
|
|
|
1. Break the statement into atomic claims that can be checked independently.
|
|
2. Choose evidence suited to each claim: current source, executable output, authoritative documentation, primary research, or direct measurement. For external technology claims, MUST apply the verification checkpoint in `technical-research`, inspecting matching evidence or resolving gaps through its Context7-first workflow.
|
|
3. Prefer the source closest to the fact. Check dates, versions, and applicability when the claim can change over time.
|
|
4. Compare conflicting evidence and explain any difference in scope or version rather than silently selecting one.
|
|
5. Label the result as confirmed, contradicted, inferred, or unknown. Keep confidence proportional to evidence quality.
|
|
|
|
Return each claim with its evidence and conclusion. Do not turn absence of evidence into evidence that a claim is false.
|