---
name: document-router
description: "文档表格规范：single consolidated skill for document/table-related Codex work. Use for 文档, 表格, PRD/SOP/specs, reports, Yuque/语雀, Notion, Obsidian, Feishu/Lark docs, Word/DOCX, PDF, spreadsheet/table, Google Docs/Sheets-targeted artifacts, presentations, research reports, knowledge-base pages, and document-skill governance. Former Chinese name: 文档路由."
---

# 文档表格规范

This is the only active user-level document workflow skill. It owns routing,
rules, gates, and validation for document-related tasks. Former document skills
are internal source/helper modules under `modules/` and must not be loaded as
active skills.
Candidate reading does not activate execution gates. Apply `Gate.md` only after
semantic confirmation that the user's actual task is document-related or
document-skill governance.

## Activate For

- Any user request involving `文档`, `方案`, `PRD`, `SOP`, `规格`, `交付`,
  `报告`, `知识库`, `会议材料`, `交接`, `验收`, `语雀`, `Yuque`, `Notion`,
  `Obsidian`, `飞书`, `Lark`, `Word`, `DOCX`, `PDF`, `Excel`, `表格`,
  `Google Docs`, `Google Sheets`, `PPT`, `PPTX`, or presentation decks.
- Requests to read, create, revise, format, verify, publish, upload, sync,
  archive, or route document-like artifacts.
- Questions about which old document skill to use, or requests to consolidate,
  audit, delete, revive, or repair document workflow rules.

## Do Not Activate For

- Ordinary coding, Unity, image generation, deployment, trading, email, or
  device-control work where no document, knowledge artifact, or deliverable file
  is requested.
- OpenAI product/API documentation lookup. Use `openai-docs` for that narrow
  documentation domain.
- Pure local file search with no document workflow; use file-search first.

## Activation Protocol

1. Classify the task: route advice, requirement clarification, writing/revision,
   artifact creation, platform read/write, research-to-document, or skill
   governance.
2. Identify destination, source of truth, artifact shape, audience, freshness
   need, and external-write intent.
3. Read `Goal.md` and `Gate.md`.
4. Read only the focused internal references selected by the route below.
5. Use internal helper script files or source package folders under `modules/`
   only as implementation helpers, not as active skills.

## Route

- General writing standards, delivery-state labels, PRD/SOP/spec/handoff
  structure, requirement clarification, positive execution wording, and current
  version concept purity: read `references/workflow-rules.md`.
- Yuque/语雀, ArmyGroup planning, Notion, Obsidian, Feishu/Lark, platform
  credentials, live read/write/publish/read-back, and external sync rules: read
  `references/platform-rules.md`.
- DOCX/Word, Google Docs-targeted files, PDF, spreadsheets/tables, Google
  Sheets-targeted files, presentations/PPTX, render/export/visual QA, and local
  artifact paths: read `references/artifact-rules.md`.
- Deep research reports, academic-style evidence, Clawdbot docs, ArmyGroup
  domain planning, and domain-specific documentation: read
  `references/research-and-domain-rules.md`.
- Old-skill provenance, internal helper locations, module paths, and
  consolidation coverage: read `references/source-package-map.md`.
- Duplicate, similar, and conflicting rule decisions: read
  `references/rule-resolution.md`.

## Output

For route-advice tasks, return the selected internal route, why it fits, required
inputs, external effects, blockers, and validation gates. For execution tasks,
perform the routed workflow and preserve exact status claims: planned,
inspected, generated, modified, written back, uploaded, exported, rendered, or
verified only after the matching tool step succeeds.