Community写作与编辑github.com

writing-order

通用文生文写作与改稿秩序规程(Writing Order)。当用户要求起草、扩写、改写、精简、润色或审校任何文本时启用。按“入场底线—篇章脉络—标题拟定—语句表达—成稿裁剪—底稿修订”的执行路线,将信息组织为逻辑自洽、边界清晰、易于阅读的作品。

writing-order 是什么?

writing-order is a Claude Code agent skill that 通用文生文写作与改稿秩序规程(Writing Order)。当用户要求起草、扩写、改写、精简、润色或审校任何文本时启用。按“入场底线—篇章脉络—标题拟定—语句表达—成稿裁剪—底稿修订”的执行路线,将信息组织为逻辑自洽、边界清晰、易于阅读的作品。.

兼容平台~Claude Code~Codex CLI~Cursor
npx skills add https://github.com/rc8s2242sr-cmd/writing-order/tree/HEAD

Installed? Explore more 写作与编辑 skills: steipete/notion, langchain-ai/langchain, bytedance/podcast-generation · View all 6 →

在你喜欢的 AI 中提问

打开一个已预加载此 Agent Skill 的新对话。

文档

Writing Order

This protocol applies to all text generation, expansion, rewriting, condensation, and proofreading tasks, and is not tied to any specific discipline or genre. The fundamental purpose of writing is to organize scattered information into a logically coherent, clearly bounded, and easy-to-read piece of work. Accuracy and professional depth are only intrinsic attributes of a work, not its entirety; a text that looks clear, smooth, and engaging at first glance is the basic prerequisite for a finished manuscript.


I. Entry Baseline: Choose Approach Based on Task, Maintain Generation Boundaries

Upon receiving a task, first identify the task type and scope of content; do not mechanically apply the full set of actions:

  1. Choose approach based on task type:

    • Short direct reply or single paragraph explanation: Clearly establish the facts and write the sentences directly; do not force chapter divisions or invent subheadings.
    • Drafting a multi-section long article, expanding an outline, or restructuring a full text: Fully follow the path of "build the chapter structure → freely write a smooth first draft → independently screen and trim."
    • Condensing an existing text: Directly proceed to the trimming approach in Section V; reduce length by cutting out marginal content in bulk, preserving the complete structure of core sentences.
    • Revising an annotated file or an existing manuscript: Simultaneously activate the manuscript revision protocol in Section VI.
  2. Only fill in logic and syntax, do not fabricate facts: Expansion or polishing is only used to clarify logical connections and complete sentence components. It is strictly forbidden to invent unprovided facts, data, or causal details just to make the chain of reasoning complete. When key facts are missing, leave a placeholder or confirm with the user.

  3. Understand the communication intent, do not leave traces of the explanation in the main text: Reminders, clarifications, or annotations from the user in the dialogue or document must first be understood by the writer in terms of their spirit and intention, and then implemented in the generated text. They are strictly forbidden from being written directly into the main text. When the user points out an error or inappropriate content, the revised manuscript must be as clean as if the mistake was never made. It is strictly forbidden to leave disclaimers like "excluding [item]" or supplementary explanations in the title or main text.

    • User annotation input:

      "I asked you to make Yu Xiang Rou Si (Fish-Fragrant Shredded Pork). Why are there tomatoes in it? Have you ever seen Yu Xiang Rou Si with tomatoes?"

    • Disordered revision (incorporating conversational cues and excuses into the main text):

      "[Presented a new dish: named 'Yu Xiang Rou Si (No Tomatoes)', along with some textual explanation of 'Why Yu Xiang Rou Si does not contain tomatoes']"

    • Orderly revision:

      "[Presented a new dish: named 'Yu Xiang Rou Si'. There are no tomatoes in it, and there is no explanation about tomatoes.]"


II. Chapter Structure: Chapter Content is Mutually Independent, Progressing Along Natural Logic

The skeleton of a multi-chapter text is built on the principle of "pure content within chapters, mutual independence between chapters, and minimal transitions at boundaries":

  1. Pure within chapters, independent between chapters: The logical integrity of the full text is supported by all chapters together. Each chapter should only contain content of the same category and dimension. Different chapters must have clear boundaries and substantially independent content; neither foreshadow details from later chapters nor repeat content from earlier ones (e.g., when stating final results, do not reiterate the formation process described earlier, except for a concluding summary paragraph).

  2. Minimal transitions at boundaries: While chapter content remains independent, use only one or two simple bridging sentences at the boundaries to maintain the flow of thought for a first-time reader (e.g., state what the previous section resolved and what this section will address; or clarify the role of this section within the overall framework). Strictly avoid directory-style announcements like "Section X elaborates on... Section Y explains..." and avoid nested mini-introductions or summaries within each section.

  3. State the motive first, then progress along natural logic:

    • Before unfolding a series of specific steps, mechanisms, or details, use one short sentence to clarify the background or goal the section addresses. This prevents a reader from knowing every word but not understanding the purpose of the actions.
    • Each block focuses on a single core subject. Whether describing objective natural phenomena or human practices, embed specific concepts, elements, or details as filler within a chain of "originatory motive → internal law or evolutionary direction → specific operational or evolutionary mechanism → final outcome or state." Avoid simple noun listings (like reading a menu).
    • When analyzing problems or limitations, point directly to objective contradictions or unmet needs. Never invert "not yet adopting a certain method" into the problem itself.

    Example A: Objective natural evolutionary scale

    • Disordered writing (listing characteristics in a vacuum):

      Succulent plants in arid regions have thick, fleshy stems and leaves, stomata that open at night, and a malic acid vacuole storage mechanism. During the day, stomata are closed, and chloroplasts release carbon dioxide through decarboxylation to complete photosynthesis. (Issue: Starts by directly piling up anatomical structures and biochemical actions. A new reader doesn't know what situation this set of mechanisms evolved to handle.)

    • Orderly writing (motive first + natural logic chain):

      During the day, deserts are hot and dry. If a plant were to open its stomata during the day to absorb carbon dioxide, its internal water would evaporate rapidly (originatory motive). To balance carbon acquisition with water conservation, succulent plants evolved a daytime-nighttime carbon fixation strategy (evolutionary direction): On cool, humid nights, the plant opens its stomata, converts absorbed carbon dioxide into malic acid, and stores it temporarily in vacuoles. When the hot day arrives, the stomata close to lock in moisture. The plant then breaks down the previously stored malic acid, releases carbon dioxide, and uses sunlight to complete photosynthesis (specific evolutionary mechanism). Through this mechanism, desert plants can stably survive and reproduce in extremely arid environments (final outcome). (Note: Labels in parentheses are for comparison; they are not written into the final manuscript.)

    Example B: Human practice scale (avoid inverting "lack of means" into "the problem itself")

    • Disordered writing:

      The community library currently does not have self-service RFID borrowing/return terminals installed, nor does it have a real-time online inventory status synchronization interface. Therefore, this plan introduces self-service scanning cabinets, electronic tags, and an inventory status synchronization backend to build a closed-loop digital borrowing management system. (Issue: The reader will ask, "Why must we deploy RFID terminals and a synchronization interface?" Not using a certain technology is merely the current state; the objective inconvenience of borrowing is the actual problem.)

    • Orderly writing:

      The community library has long relied on manual paper-based records for tracking. During peak hours, residents face long waits to borrow or return books. Furthermore, residents cannot check if the book they want is on the shelf before they leave home. To address these two inconveniences, the library switches to a self-service borrowing/return mechanism and an on-shelf status disclosure mechanism. By attaching electronic tags to the library's collection, residents can scan and complete borrowing/return procedures at a terminal. The system synchronously updates the on-shelf status of each book and makes it accessible for querying via mobile app. This eliminates manual record-keeping queues and prevents residents from making a trip for nothing.


III. Title Crafting: Directly State the Core Judgment, Break Apart Forced Combinations

  1. Directly state the judgment, eliminate ambiguity: When articulating a problem, cause, or viewpoint, the subheading must explicitly state "who did what" or "what caused what." Strictly avoid phrases that are a mere list of words and lack judgment or action.

    • Disordered writing: Pain Point 1: Information Lag and Cross-Departmental Scheduling (Issue: "Information lag" is a problem, but "cross-departmental scheduling" is a neutral term; it doesn't clarify what the issue with scheduling is.)
    • Orderly writing: Pain Point 1: Delayed information synchronization disrupts cross-departmental scheduling
  2. Break apart forced combinations, preserve the causal chain: Strictly avoid forcing two substantially independent, superficially related things into the same title. If a single subject-verb-object structure can explain it clearly, do not use coordinating conjunctions like "and," "or," "together with," commas, etc., to stitch together multiple items. (An exception is only allowed when multiple causes objectively and inseparably lead to the same outcome and cannot be combined into one concept). Conversely, if the preceding and following steps inherently form a smooth, coherent causal chain, they are the same thing; condense them directly into a complete judgment rather than artificially splitting them to pad word count.

    • Disordered writing (forced combination): Limitation 1: General Large Model Lacks Professional Knowledge and Has Poor Grammar (Issue: Forces two independent, superficially related things into one title.)

    • Orderly writing (split into independent points):

      Limitation 1: General large model lacks necessary domain expertise;

      Limitation 2: General large model has not yet mastered syntax rules for geoscience code

    • Boundary reminder (don't force-split a coherent chain): If the logic itself forms a smooth, coherent causal chain, condense it directly into a complete judgment (e.g., Vague review standards slow down overall delivery progress). Do not artificially split it into two titles to pad word count (e.g., 1. Vague review standards cause rework; 2. Rework slows down overall delivery).

  3. Remove redundant modifiers, keep necessary particles, do not force symmetry: For modular or object-oriented titles, also remove layered modifiers, but retain necessary prepositions and particles like "for" or "regarding." Avoid cramming multiple two-syllable nouns into a chain. The goal of a title is always to be understood at a glance. It is better to have uneven lengths than to force a neat four- or six-character pattern and squeeze the meaning.

    • Disordered writing: Mechanism for Sorting and Categorizing Multi-Channel Feedback Collection and Historical Ticket Archiving
    • Orderly writing: Mechanism for Categorizing Feedback Tickets

IV. Sentence Expression: Use Plain, Natural Language; Complete, Breathable Syntax

  1. "Speak human" with plain written language: Use clean, precise modern written language to directly state facts and reasoning. Avoid words that are only common in small circles or that can be easily misinterpreted at face value. Guard against the extremes of both "obscure coinages" and "false colloquial figures of speech":

    • Do not coin words or create self-made abbreviations: Widely accepted abbreviations are allowed; strictly avoid creating obscure, semi-classical words by following word formation habits. Strictly avoid forcibly compressing normal phrases into awkward, self-made acronyms to save characters.
    • Do not use vague words, awkward colloquial short words, or exaggerated modifiers: Do not use words with fuzzy boundaries to obscure specific facts; directly state what action was taken. Do not use awkward, contracted colloquial phrases. When stating objective facts, refrain from dramatic words like "virtually," "completely," or "extremely." If two adjacent two-syllable verbs represent independent processes at different levels (e.g., individual "survival" and population "reproduction"), separate them with a comma, and do not fuse them into a single unit following the inertia of four-character idioms.
    • Do not use analogies or slogan-like parallelism: When explaining a principle, state the logic directly. Analogies are strictly forbidden. Slogan-like parallelism, self-made "X-character formulas," quantifier parallelism, and forced four- or six-character symmetrical clauses are strictly forbidden.
    • Choose common abstract words based on actual effect: Do not implement a blanket ban on common, high-frequency abstract words. Words are tools: use them if they make the meaning more precise and the logic more powerful; do not use them just to fill a void or create parallelism.
  2. Complete subject-verb-object structure, do not implicitly change subjects, do not cause back-tracking re-reading:

    • Every single sentence must have a clear subject, verb, and object. Do not write truncated, headless sentences. Strictly avoid telegraphic chopped sentences that omit grammatical components, and avoid unnatural inversions. For the subject position, prioritize using a "modifier + de + head noun" structure to establish a solid entity; avoid using loose clauses as subjects. For the predicate position, prioritize a natural verb-object word order; avoid awkward nominalized compression (e.g., write "difficult to draw a reliable conclusion," not "drawing a reliable conclusion difficulty big").
    • When the subjects of consecutive clauses are different, or when temporal/scope adverbials follow a semicolon or conjunction, write the subject of the current clause explicitly so the reader does not have to mentally switch subjects.
    • Write the central noun in full for each item in a list of varying lengths (e.g., write "self-service borrowing/return mechanism and on-shelf status disclosure mechanism," not "self-service borrowing/return and on-shelf status disclosure mechanism"). This prevents the reader from having to backtrack and re-parse at the end of the sentence.
  3. Actively add punctuation for breath based on meaning levels: If a sentence is too long without punctuation, it irritates the reader. Resolutely insert commas between two sequential verb-object actions, after long prepositional or temporal phrases, and before a purpose phrase starting with "in order to." While shortening the sentence with commas, retain conjunctions like "and" to keep the meaning flowing without breaking it.

  4. Only use affirmative sentences for positive statements: Directly state "what it is, how it works, what outcome it produces." Avoid constructions like "it is not A, but B" or "it is not that..." that set up a hypothetical target and then defend against it. Do not add unnecessary negative preamble before a positive statement.

    Comprehensive comparison example:

    • Disordered writing:

      The purpose of cross-team project post-mortems is not to assign blame, but to act like installing a compass to calibrate direction for the team, achieving 'see clearly, correct accurately, land stably'. However, traditional post-mortems struggle to identify root causes of anomalies. This mechanism collects execution records from all stages before the meeting, compares them to the plan to identify key deviations, assigns a responsible person to formulate improvement measures, and achieves business enablement leap. (Issues: Contains "not... but..." argument, compass analogy, three-character slogan, awkward compression "root cause location difficult", a 50+ character run-on sentence without punctuation listing verb actions, and empty "enablement leap".)

    • Orderly writing:

      Cross-team project post-mortems aim to identify execution deviations and optimize future collaboration processes. Previously, post-mortems often relied on oral review, making it difficult to accurately pinpoint the root cause of problems. The improved post-mortem mechanism proceeds in three steps: Before the meeting, consolidate execution records from all stages, compare them against the original plan, and identify key discrepancies. During the meeting, analyze the discrepancies, verifying the causes item by item. After the meeting, have the responsible person formulate specific corrective actions and follow up to verify their implementation in the next cycle.


V. Final Trimming: First Write the First Draft Smoothly, Then Cut Out Marginal Content in Blocks

If you try to force word limits and eliminate filler while drafting, the text easily becomes stiff, dry, and feels like "deceptive telegram-speak." Drafting and condensing must be separated into two sequential steps (for direct dialogue output, first write a smooth draft internally, then screen and trim before output; for file reading/writing, first write a complete draft, then re-read the full text, trim, and overwrite):

  1. Step One: Write a smooth first draft freely: Temporarily ignore any word count limits. Focus on writing the natural logical chain smoothly, ensuring each sentence has a complete subject, verb, object, and necessary particles and connectors.

  2. Step Two: Independently screen and trim: Adopt the perspective of a first-time reader to re-read the first draft. While checking titles and long sentence punctuation, subtract material by applying three criteria:

    • Marginal Cutting Principle (only worry about this chapter's own business): The overall completeness of the text is the responsibility of all chapters, but the text within a chapter (except for a very small number of necessary transition sentences) is only responsible for that chapter. Do not overstep to serve the whole text or other chapters. Any tangential content not related to the chapter's main point, whose inclusion or exclusion does not affect the establishment of the chapter's core meaning (e.g., casually noting a relationship with another chapter, or stating an obvious premise from the context), should be cut entirely—as a whole sentence or whole block. Multiple fragmented steps leading to the same final result should be merged into that single result.
    • Mutual Exclusivity Principle (if you write the positive side, don't write the negative): When a thing has only two mutually exclusive aspects logically, and the text has already positively stated that one aspect holds true, do not write an additional sentence stating that the other aspect does not hold true.
    • Word-Reduction-Without-Losing-Syntax Principle: The only way to compress word count and remove redundancy is by "cutting out marginal content in blocks and merging fragmented listings." Do not use the approach of "keeping every content point but removing main verbs, subjects, objects, and logical connectors" to force word counts down. The core sentences left after trimming must still have a complete structure and proper logical connectors.

    Three-way comparison example of length trimming (reducing a 230-word first draft to about 120 words):

    • First Step Draft (fully elaborated, but includes tangential content from other sections and negative-side fluff):

      3.2 Exhibition Description Card Writing To help ordinary visitors understand the historical value of museum collections, the curation team needs to write display cabinet description cards for each first-tier exhibited cultural relic. The writers do not directly copy the obscure original text from archaeological excavation reports. Instead, they combine the background of the artifact's excavation and its function to extract core historical information (this basic historical material will also be shared with the audio guide team for recording scripts). Subsequently, the staff members sequentially complete the first draft, check for typos, verify dates, lay out the card size and font, and print and install the acrylic card, explaining the date, function, and craftsmanship features within a 200-word limit, so that visitors can understand the artifact's origin during a short browse.

    • Incorrect Condensation (unwilling to cut content points, relying on removing grammatical components to force word count → pseudo-telegram style, ~85 words):

      3.2 Exhibition Description Card Writing For visitors to understand artifact value, not copy obscure dig report text, combine excavation background with use to extract core info (shared with audio guide team for script), after drafting, proofreading, date verification, layout, printing and installation, within 200 words state date, use, craftsmanship, assist visitors short browse understand origin. (Issue: All tangential content is kept; word count is reduced by deleting subjects, verbs, and connectors. The result is stiff and disjointed.)

    • Orderly Condensation (Step Two: Subtraction using three criteria → ~120 words):

      3.2 Exhibition Description Card Writing The exhibition description card helps ordinary visitors understand a cultural relic's origin during a short browse. Writers combine the artifact's excavation background and actual function to extract core historical information from the archaeological data, explaining its date, purpose, and craftsmanship features within a 200-word limit. After factual verification, the text is printed and installed next to the display case. (Trimming Retrospective: ① Marginal Cutting: The bracketed "shared with audio guide team" relates to another chapter's business; cutting it doesn't affect this section's validity, so it's cut entirely. ② Mutual Exclusivity: Since we positively state "extract core historical information from archaeological data," the sentence "do not directly copy obscure original text" is immediately removed. ③ Merging fragmented listings: "checking for typos, verifying dates, font layout, printing and installing acrylic" is merged into "after factual verification, printed and installed." The remaining sentences still have a complete subject-verb-object structure and are smooth and easy to read.)


VI. Manuscript Revision: Make Only the Minimum Necessary Changes When Modifying Existing Documents

This section remains frozen during routine new text generation; it is automatically activated only when detecting that an existing stored document is being modified (e.g., revising a .docx or .md manuscript or processing an annotated file):

  1. Align first, then modify: When encountering multiple annotations or structural adjustments, first restate your understanding of the annotations and list the proposed changes. Confirm with the user before making any modifications to the original manuscript.
  2. Guard the manuscript, only modify the specified points: Strictly lock onto the manuscript file most recently specified by the user. Only modify the areas indicated by annotations or the specifically requested adjustments. Preserve all other user-approved text verbatim. Strictly avoid taking the initiative to "polish on the side" or revert changes.
  3. Maintain existing formatting and object styles: When modifying a document with fixed formatting or specialized objects, strictly adhere to the styles and object formats already established in the document (e.g., if the original document uses native formula objects to write equations and variables, and specific styles for tables and numbering, all modifications must use the same native objects and styles. Do not mix in plain text characters as substitutes.)

相关技能