Research Document Workflow

Core Contract

Keep research content standards independent from storage platforms. Use one canonical Markdown-first document for the shared body: headings, paragraphs, lists, block quotes, links, tables, code blocks, and LaTeX formulas should remain the same unless the target demonstrably requires a small conversion. The task-specific skill owns what the document means and which sections are required; this skill selects the destination backend, loads the matching platform adapter, applies only the necessary platform deltas, performs the write, and verifies the durable result.

Do not create separate Feishu, Notion, and Obsidian versions of the same content skill or template. Maintain one Markdown structure and three thin delivery adapters (feishu-doc-workflow, notion-doc-workflow, obsidian-doc-workflow) so field definitions, evidence standards, wording, and acceptance gates cannot drift.

Platform Resolution

Resolve the target in this order:

1. Explicit user instruction (写到飞书 / 写到 Notion / 写到 Obsidian/vault).
2. URL or path in the request (feishu.cn / larksuite.com → Feishu; notion.so → Notion; vault .md path / WorldModelVault folder → Obsidian).
3. Platform of an existing durable document being updated (never silently migrate).

The user normally supplies a link or an explicit destination. If none of the above resolves a single platform, ask one concise destination question. For a new deep dive without an explicit destination, use Notion. Do not silently duplicate across platforms.

Never silently migrate, duplicate, or delete an existing durable document. A platform change requires an explicit target or a user-approved migration task.