• work_dir

  : Root working directory

• resume_path

  :

  <work_dir>/.work/resume.md

• jd_ids

  : List of JD IDs (sorted by matching degree)

• run_id

  : Current run ID

1. Experience/Project Sorting: Move the project most relevant to the current JD to the top of its section
2. Intra-Project Outcome Sorting: For each substantial project's outcome sub-entries, move the metrics that fit the current JD to the top
3. Skill Section Sorting + Wording: Move the skills/tools emphasized by the JD to the top of the skill section; adjust the wording of introductory and outcome sentences to align with JD keywords (without altering facts)

[Need User Confirmation]

1. Never add projects, skills, or company experiences that do not exist in the original resume
2. Never fabricate specific numbers (user volume/growth rate/revenue, etc.); use

   [Please Fill in: xxx]

   as a placeholder for missing data
3. Never modify work periods, job titles, or company names
4. Never mention experiences not in the resume in opener.md
5. Never fabricate, infer, or fill in any content for empty entries (only title/time/department, no Action/Result description) — keep them as they are so the user can see and complete them themselves

• Keep section titles verbatim: Do not modify, split, or merge them. For example, "Work and Education Experience" cannot be split into "Work Experience" + "Education Background", and "Personal Information" cannot be renamed to "Basic Information"
• Freeze the order of top-level sections: Follow the actual order in the original resume; do not swap them (Professional Skills/Work Experience/Project Experience/Education Background are just examples and do not represent the standard order)
• Freeze paragraph addition/deletion: Do not add or delete any paragraphs; keep metadata/overview sections such as "Personal Information", "Contact Information", and "Self-Assessment" intact without deleting, renaming, or reordering their internal entries
• Do not move content across sections: Never move, copy, or reference descriptions/data/outcomes from Section A to Section B (e.g., data from project experience cannot appear under work experience entries, even if the project "occurred during that work period"); each section can only be rewritten based on the original text within it

• Freeze the number of sub-entries: Do not delete sub-entries within each experience (only shorten the wording of less relevant items, do not delete the entries)
• Keep empty entries as they are (same as A.5)
• Keep list formats verbatim: If the original resume uses list markers (

  *

  /

  -

  /

  +

  /

  1.

  , etc.) for multi-line display, the output must maintain the same markers + one item per line. It is strictly forbidden to compress multiple list items into a single paragraph of plain text (even using ";" or "," to concatenate)

• Keep proficiency terms: Do not delete proficiency-level terms such as "Proficient in", "Familiar with", "Understand", "Skilled in using"
• Do not delete tool/platform/technology names: You may adjust their order within entries (move those emphasized by the JD to the front)
• Strict constraints on merging: Only "different expressions of the same specific tool/ability" can be merged (e.g., "PS" = "Photoshop", "Data Analysis" ≈ "Data Review"); never merge abilities from different dimensions (e.g., "Platform Operation" vs "Content Planning" vs "Private Domain Operation" are different dimensions and should remain separate entries); the number of entries after merging must not be less than 80% of the original number (8 entries can be merged to at most 6-7 entries; merging into 1 entry = serious violation)

⚠️ Incorrect Example of List Compression (Must Avoid):

Original Resume (8 independent list items):
* Proficient in mainstream new media platforms such as WeChat Official Account, Video Account, Douyin, Xiaohongshu, Bilibili...
* Proficient in content planning, topic selection, copywriting...
* Familiar with user portrait analysis of various platforms...
* (...Total 8 items)

❌ Incorrect: Merge 8 items into one paragraph using ";"
Proficient in WeChat Official Account...; Proficient in content planning...; Familiar with user portrait analysis of various platforms...

✅ Correct: Keep list markers, reorder according to JD but keep entries independent
* Proficient in mainstream new media platforms such as Douyin, Video Account, Xiaohongshu... (JD emphasizes short videos, moved up)
* Proficient in content planning, topic selection, copywriting...
* (...Keep 8 independent list items)

• <work_dir>/.work/resume.md

  (Original main resume)

• <work_dir>/.work/resume.star.md

  (STAR disassembled version, if exists)

• <work_dir>/.work/jd-pool/<id>.md

  (Full JD text)

• <work_dir>/.work/jd-pool/<id>.analysis.md

  (Scoring and dimension analysis)

• Experience Sorting: Within the same section (e.g., multiple work experiences under "Work Experience", multiple projects under "Project Experience"), which entry is most relevant to the JD and should be moved forward? (Top-level sections cannot be swapped, see 🛡️B)
• Skill Sorting: Compare with the JD, move relevant skills/tools forward to form a rewrite plan for the skill section (constraints see 🛡️B Skill Section Exclusive)
• Action Supplement: Which experience's action description lacks the work methods emphasized by the JD (e.g., "Cross-team collaboration", "Data-driven decision-making") and can be supplemented based on existing facts?
• Result Gap: Which experience lacks quantitative indicators and requires inserting

  [Please Fill in: xxx]

  as a placeholder?
• Implied Information: Which experience "obviously implies" a JD focus but does not explicitly state it, allowing for light supplementation (mark with

  [Need User Confirmation]

  )?
• De-emphasized Items: Which experience has low relevance to the JD and should be moved backward or have its wording shortened? (Only shorten, do not delete the entry)
• Intra-Project Outcome Reordering: For each substantial project, move the outcome line most relevant to the JD to the top of the outcome list (if JD emphasizes Xiaohongshu → pin Xiaohongshu outcomes to the top; if JD emphasizes live streaming → pin live streaming outcomes to the top). "No changes needed" is not a valid conclusion — if there is outcome data, there must be at least one adjustment to order or wording.

1. Adjust the order of entries within the same section, placing the most relevant to the JD at the top
2. Rewrite each Action / Result section according to the conclusions, keeping facts intact and not adding new content
3. Reorder and reword the skill section according to the plan from Section 1.0
4. Insert

   [Please Fill in: <Description>]

   where quantitative data is missing; add

   [Need User Confirmation]

   where implied information is lightly supplemented

1. Have all three mandatory minimum requirements of the core task been implemented? (Project sorting / Intra-project outcome sorting / Skill sorting + wording)
2. Check each substantial entry one by one: Has the outcome line closest to the JD been moved forward? Has at least one wording adjustment been made to the introductory/outcome sentences to align with JD keywords? Have de-emphasized items been moved backward or shortened?

<work_dir>/output/<run_id>/tailored/<id>/resume.md

1. Opening: "Hello!" (fixed, do not add other salutations)
2. Self-Introduction (1 sentence): Natural and fluent Chinese, reference sentence structures:
   • "I have X years of experience in <field>, mainly responsible for <core direction>."
   • "I have been deeply engaged in <field> for X years, and am skilled in <specific ability>."
   • ⛔ Prohibited Sentence Structures: Stiff/cliché expressions such as "I am a job seeker for..." "I possess..." "Available for this position" "Your company"
3. Highlight Experience (1-2 sentences): Highlight one specific experience most relevant to the JD, clearly stating what was done and what outcomes were achieved (must be truly present in the resume)
4. Express Intention (1 sentence): Naturally express the willingness to communicate, e.g., "I am very interested in this position and hope to have the opportunity to learn more."

Hello! I have 3 years of new media operation experience, mainly responsible for content planning and growth of Xiaohongshu and Douyin accounts. In my previous job, I led a brand cold-start project, growing the account followers from 0 to 200,000 in 6 months, with a stable hit rate of over 15%. I am very interested in this position at your company and look forward to further communication!

• Only mention experiences present in the resume, do not fabricate (same as 🛡️A.4)
• If an experience has a

  [Please Fill in: xxx]

  placeholder, do not reference the specific numbers of that experience in the opening message
• If the opening message mentions an experience with a

  [Need User Confirmation]

  mark, keep the prompt for the user to verify

<work_dir>/output/<run_id>/tailored/<id>/opener.md

undefined

• Title

  # Change List · Compared to Main Resume

• Section

  ## ℹ️ No Changes Made to Main Content for This Position

  , stating the reason (e.g., "The resume has only 1 substantial project, and this JD's requirements are highly consistent with those of already processed positions, leaving no room for differentiation")
• Section

  ## 💡 Suggested Supplements (Need Your Manual Completion)

  , providing specific gap prompts targeted at this JD

undefined

1. [Section Name]: "<Original Text>" → "<Revised Text>"
   • Reason: <What in the JD triggered this change>

1. Moved "<Section>" to "<New Position>"
   • Reason: <This direction is the top priority of the JD>

1. [Section Name] Result Section:

   [Please Fill in: <Specific Description>]

   • Reason: <The resume lacks specific numbers here, and the JD emphasizes data-driven approaches>

1. [Section Name]: "<Revised Content>" [Need User Confirmation]
   • Reason: <Inference basis>

1. Moved "<Section>" backward or shortened its wording
   • Reason: <This experience has low relevance to the JD>

1. Order Adjustment: Moved "<Entry Summary>" to the top
   • Reason: <The JD emphasizes this skill as a key focus>
2. Wording Rewrite: "<Original Text>" → "<Revised Text>"
   • Reason: <Explanation>
3. Entry Merging: "<Entry A Summary>" + "<Entry B Summary>" → "<Merged Entry>"
   • Reason: Semantically highly overlapping, merged entry retains all key information

The following suggestions are based on the current JD requirements. You need to supplement real information to update the resume; AI cannot fill this in for you.

• "<Original Entry>" — Suggested revision: "<Rewritten Example>", aligned with the JD's requirement of "<JD Original Keyword>"

• Currently, all <X> entries are marked as "<Proficiency Term>". It is recommended to distinguish between "Proficient / Familiar / Understand", referring to the JD's key skills: <List the 2-3 highest-weighted skill terms in the JD>

• "<Entry Summary>" — No relevant mention in the JD, low relevance to the position

Re-emphasis: **The code block above is a writing example; each section is only output if that type of change actually occurred. Empty sections are never output.** The same applies to the "💡 Skill Section Optimization Suggestions" section; each of the three sub-items is judged independently and omitted if not applicable.

Write to `<work_dir>/output/<run_id>/tailored/<id>/changelog.md`.