doc-type-routing

Determination of Document Type and Direction

The first step in official document writing that is most prone to error and should be determined first:If the wrong document type is chosen, no matter how well it is written afterward, it is useless(a report written as a request for instructions, a letter written as a notice, a decision and a resolution used interchangeably). This skill structures this step; after determination, hand off to the root SKILL.md(Official Document Writing) for drafting.

Document Index

prompts/core/workflow.md            # 判断流程与文种路由规则（主源）
prompts/core/drafting-thinking.md   # 易混文种三维辨析、行文方向与谋篇对应（主源）
docs/references/document-types.md        # 各文种适用场景与边界说明（读者文档）

Three-Dimensional Determination Method

Direction: upward (to a superior) / downward (to a subordinate) / parallel or non-subordinate / publicly released.
Purpose: request approval, report circumstances, deploy and execute, reply, inform, negotiate, record, submit for deliberation, publish.
Whether a response is needed: requires an official reply (request for instructions), requires deliberation (proposal), is itself a response (official reply / reply letter), not mandatory (report / notice / circular).

Once these three are determined, the document type basically converges uniquely.

Quick Routing

Request approval from a superior → request for instructions(one matter per document, addressed to only one superior, ending with "Whether this is appropriate, please instruct")
Reply to a subordinate's request for instructions → official reply(first cite the incoming document's title and document number)
Report to a superior, no reply required → report(do not include matters requesting approval)
Deploy/convey execution, approve and transmit or forward → notice
Propose principles and measures → opinion; major decisions/rewards and penalties → decision; adopted by meeting vote → resolution
Negotiation/inquiry/reply/request for approval between non-subordinate or parallel organs → letter
Publicly announce important or statutory matters → announcement; matters that must be complied with within a certain scope → public notice
Matters agreed upon at a meeting → minutes; government submits to the people's congress at the same level for deliberation → proposal
Compile news developments/special-topic situations (not statutory official documents) → briefing / special situation report / reporting materials

High-Frequency Error-Prone Distinctions

Report vs. request for instructions: a report reports, does not require a reply, and may be comprehensive; a request for instructions seeks approval, must await an official reply, and covers one matter per document. Matters requesting approval must not be included in a report.
Decision vs. resolution: a decision may be made directly by an organ; a resolution must be voted on at a meeting and issued in the name of the meeting.
Circular vs. public notice: a circular is internal (commendation/criticism/information); a public notice is external (announces matters that must be complied with, with mandatory force).
Announcement vs. public notice: an announcement declares important/statutory matters domestically and internationally, and the issuing organ is at a relatively high level; a public notice is directed at a certain scope.
Letter vs. notice/request for instructions: For non-subordinate or parallel organs, a letter shall always be used, and it shall not be upgraded because the matter is important.

No agent environment (web/offline)

This skill is purely judgment-based and does not connect to the internet; all its criteria come from prompts/core/workflow.md and prompts/core/drafting-thinking.md, and these two have been fully inlined into the offline system prompt.
Therefore, when there is no agent/skill environment, no additional operation is needed: paste dist/offline/default/system_prompt.mdand it already includes the guidelines for determining the document type and direction of communication, so the model can be directly asked to first determine the document type and then draft.

Boundaries

Only determine the document type and direction, and do not generate the body text; after determination, hand it over to "Official Document Writing" to draft according to the corresponding spec.md .
Criteria shall always be based on prompts/core/workflow.md、prompts/core/drafting-thinking.md as the primary source; this skill does not copy the rules.
After the draft is completed, if you want to check the document type, closing expressions, and whether the sections are complete, switch to document-qa（src/scripts/check_sections.py）。