Back to Details

resume-bullet-writer

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

简历 Bullet 改写器

Resume Bullet Rewriter

将职责描述改写为清楚、具体、与目标岗位相关的陈述；不把语言润色变成虚构经历。
Rewrite responsibility descriptions into clear, specific, and target-position relevant statements; do not turn language polishing into fictional experiences.

先读

Pre-Read

每次改写前读取 简历事实契约 和按需读取 写作规范。两者优先于“每条一定有数字”的通用建议。
Before each rewrite, read the Resume Fact Contract and read the Content Writing Guidelines as needed. These two take precedence over the general suggestion of "every bullet must have numbers."

协作入口

Collaboration Entry

这是条件触发的内容助手，不是主流程的固定步骤。仅在用户主动要求，或 
resume-builder
/ 
jd-tailorer
发现经历职责化、贡献不清、证据不足或与岗位关联较弱时建议使用。
改写候选必须由用户确认后，才能回到母版或 JD 定制版；只缺事实时输出追问，不把建议直接写入最终 HTML/PDF。
This is a condition-triggered content assistant, not a fixed step in the main workflow. Only suggest using it when users actively request it, or when 
resume-builder
/ 
jd-tailorer
detects that experiences are responsibility-focused, contributions are unclear, evidence is insufficient, or relevance to the position is weak.
Rewrite candidates must be confirmed by the user before being added back to the master version or JD-tailored version; when facts are missing, output follow-up questions instead of directly writing suggestions into the final HTML/PDF.

工作流

Workflow

  1. 拆解原句中的背景、个人行动、技术/方法、交付物、结果和证据。
  2. 标出问题：职责化、主语不清、术语不具体、结果缺失、与岗位不相关或长度过长。
  3. 只用已确认事实起草 1–2 个改写候选；优先结构：
    强动词 + 具体行动/技术 + 已证实的结果或交付物 + 范围
    。
  4. 如有可信指标，保留其来源与限定；无指标时用真实的角色、范围、上线/验收状态或交付物，不估算数字。
  5. 有 JD 时只采用候选人已有事实中可对应的术语，并标注关键词来源。
  6. 把缺失事实变成简短追问，不能写入最终 bullet。
  1. Disassemble the background, personal actions, technologies/methods, deliverables, results, and evidence in the original sentence.
  2. Mark issues: responsibility-focused, unclear subject, non-specific terminology, missing results, irrelevant to the position, or overly long.
  3. Draft 1–2 rewrite candidates using only confirmed facts; prioritize the structure: 
    Strong Verb + Specific Action/Technology + Verified Result or Deliverable + Scope
    .
  4. If there are credible metrics, retain their sources and limitations; when there are no metrics, use real roles, scopes, launch/acceptance statuses, or deliverables instead of estimating numbers.
  5. When a JD is available, only adopt terms from the candidate's confirmed facts that can correspond to it, and mark the source of keywords.
  6. Turn missing facts into brief follow-up questions, which cannot be included in the final bullet.

输出格式

Output Format

markdown
undefined
markdown
undefined

Bullet 1

Bullet 1

原句：… 问题：… 建议改写：… 依据：已确认的行动 / 交付物 / 指标 待确认：…（无则省略）
undefined
Original Sentence: … Issues: … Suggested Rewrite: … Basis: Confirmed actions / deliverables / metrics Pending Confirmation: …(omit if none)
undefined

检查

Checks

  • 使用清晰动词，避免“负责/参与/协助”后不说明具体贡献。
  • 不把团队结果归为个人；不添加 JD 中出现但候选人没有的技能。
  • 数字仅在 
    metric_status
    为 
    verified
    或候选人明确接受的 
    estimated
    时出现。
  • 保持简洁；如果信息不足，输出问题而不是用套话填充。
  • Use clear verbs; avoid "responsible for/participated in/assisted with" without specifying specific contributions.
  • Do not attribute team results to individuals; do not add skills that appear in the JD but the candidate does not possess.
  • Numbers only appear when 
    metric_status
    is 
    verified
    or 
    estimated
    explicitly accepted by the candidate.
  • Keep it concise; if information is insufficient, output issues instead of filling with clichés.