fact-check

Fact-Check

学術文書中の記述をカテゴリ別に分類し、サブエージェントによる並列検証を経て、構造化されたMarkdownレポートを生成する。

Process

digraph factcheck {
  "Read input file" -> "Detect available tools";
  "Detect available tools" -> "Existing report?";
  "Existing report?" -> "Full check (Phase 1-3)" [label="No"];
  "Existing report?" -> "Incremental check" [label="Yes"];
  "Incremental check" -> "git diff to find changes";
  "git diff to find changes" -> "Classify new/changed statements";
  "Classify new/changed statements" -> "Dispatch agents (Phase 2)";
  "Full check (Phase 1-3)" -> "Classify all statements";
  "Classify all statements" -> "Dispatch agents (Phase 2)";
  "Dispatch agents (Phase 2)" -> "Merge results (Phase 3)";
  "Merge results (Phase 3)" -> "Write report";
}

Phase 0: Tool Detection

Before any processing, detect which tools are available for verification. Check for these tool name patterns in the current environment:

Tool	Detection Pattern	Purpose
Zotero	mcp__zotero__* tools exist	User's reference library
PubMed	mcp__plugin_pubmed_PubMed__* tools exist	Academic paper search
Web Search	WebSearch tool exists	General information search
Academic DB skills	database-lookup, paper-lookup skills exist	Various academic databases

Build a tool availability summary to include in each agent's prompt:

## Available Tools
- Zotero: [specific tool names] [Available/Not Available]
- PubMed: [specific tool names] [Available/Not Available]
- Web Search: WebSearch [Available/Not Available]
- Academic DB: [specific skill names] [Available/Not Available]

## Tool Priority
1. Zotero (user's existing library)
2. Academic databases (PubMed, etc.)
3. Web search (fallback)

Phase 1: Classification

Read the input file and classify each meaningful statement into one of 6 categories.

Categories

Category	Description	Criteria
fact	Verifiable factual statement	Independently verifiable numbers, dates, measurements, events
definition	Definition of a term or concept	Explains what something is or means
common-knowledge	General knowledge, no citation needed	An undergraduate in the field could write without citing
claim	Interpretation or argument	Contains judgment; based on past data or evidence
prediction	Forecast about the future	Forward-looking; based on trends or theory
opinion	Subjective judgment	Personal assessment or value statement

Classification Boundaries

• fact vs common-knowledge: Could an undergraduate in this field write this without citing a source?
• claim vs prediction: Past data interpretation → claim. Future projection → prediction.
• fact vs claim: Independently verifiable data → fact. Requires interpretation → claim.

Output Format

Create a structured classification list. For each item, record:

• An ID (sequential number)
• The original text
• The assigned category
• The surrounding context (paragraph or section it appears in)

Phase 2: Agent Dispatch

Dispatch 6 agents in parallel using the Agent tool, one per category. Each agent receives:

1. The list of statements assigned to its category (with IDs and original text)
2. The full document text for context
3. The tool availability summary from Phase 0

Use the Agent tool with subagent_type matching the plugin agent names:

• fact-check:fact-verifier
• fact-check:definition-verifier
• fact-check:common-knowledge-verifier
• fact-check:claim-verifier
• fact-check:prediction-verifier
• fact-check:opinion-verifier

Skip any category that has zero items — do not dispatch an agent for empty categories.

Agent Prompt Template

For each agent, construct a prompt containing:

1. The agent's task description
2. The list of items to verify (with IDs)
3. The full document text
4. The tool availability summary
5. The expected output format (matching the report template tables)

Phase 3: Report Generation

1. Collect results from all agents
2. Read the report template (this plugin's templates/report-template.md)
3. Fill in the template:
   • {{file_path}} → absolute path of the input file
   • {{datetime}} → current date and time (YYYY-MM-DD HH:MM)
   • {{commit_hash}} → current HEAD commit hash (short form, 7 chars)
   • {{repo_type}} → "元リポジトリ" or "factcheck内リポジトリ"
   • {{available_tools}} → comma-separated list of detected tools
   • {{check_mode}} → "全体チェック" or "差分更新"
4. Fill each category table with agent results
5. Fill the 検証コミット column with the current commit hash
6. Calculate summary counts (件数, 問題あり, 未確認) from all tables
7. Create factcheck/ directory next to the input file if it doesn't exist
8. Write the report to factcheck/<filename-without-ext>-factcheck.md

Incremental Check (Diff Update)

When an existing report is found at the expected output path:

Step 1: Determine git context

Case A — Input file is in a git repo:

• Use that repo's commit history
• Read the last verified commit from the existing report's 最終検証コミット metadata
• Run: git diff <last_commit>..HEAD -- <input_file_path>

Case B — Input file is NOT in a git repo:

• Check if factcheck/.git exists (independent repo created on first run)
• If factcheck/.git does not exist → this is actually the first run. Do full check.
• If factcheck/.git exists:
  • Copy the current input file to factcheck/_source/<filename> (overwrite)
  • Run git diff in the factcheck repo to detect changes vs. the last committed version
  • After detecting changes, stage and commit the updated source

Step 2: Process diff

• Added lines: Classify new statements and add as new items to verify
• Changed lines: Match to existing report items by original text, mark for re-verification
• Deleted lines: Remove corresponding items from the report
• Unchanged lines: Keep existing report results as-is

Step 3: Dispatch agents for new/changed items only

Step 4: Merge results into existing report and update metadata

Update 最終検証コミット and 最終検証日時 in the report header.

Git Repo Setup (Case B — First Run, Non-Git File)

When the input file is not in a git repository and no factcheck/ directory exists:

1. Create factcheck/ directory next to the input file
2. Run git init inside factcheck/
3. Create factcheck/_source/ directory
4. Copy the input file to factcheck/_source/<filename>
5. git add and git commit the source copy
6. Proceed with full check

Constraints

• NEVER modify the input file
• Always create the report as a new file (or update existing on incremental check)
• Agents must only use the tools explicitly listed in their prompt
• Each agent receives the full document context