add-experience

Project Experience Supplement Skill

Used to supplement project experience and work information in the career materials library, automatically syncing and updating all related files.

Use Cases

• Add new project experience to a certain company
• Fill in the missing fields listed in timeline.md
• Update the detailed information of an existing project
• Supplement work achievements and quantitative data

How to Use

Users can provide information in the following ways:

1. Free text: "I built a budget system at ottno, covering 200+ stores, improving forecast accuracy by 30%"

1. Structured description: "Supplement EY's employment period: July 2018 to June 2020, city: Shanghai"

2. Simple trigger: "Add an ottno project" (the skill will guide you through filling it in)

Execution Steps

Step 1: Parse user input

Extract from user input:

• Target company (ey or ottno)
• Supplement type (new project vs filling in missing fields)
• Information already provided

Read related files to understand the current state:

• materials/timeline.md - Check fields to be supplemented
• materials/experience/{company}/overview.md - Understand the status of company materials
• materials/experience/{company}/core-projects.md - Check existing projects

Step 2: Identify missing information

Based on the supplement type, check for missing required fields:

New projects require：

• Project name
• One-sentence positioning (background + business goal + mechanism/system)
• Role scope (independent/leading/cross-departmental, coverage scope)
• Key actions (3-5 items)
• Quantitative results (2-4 items)
• Transferable skill tags

Filling in fields requires(refer to the fields to be supplemented in timeline.md):

• EY: employment period, city, business line, core clients, representative achievements
• ottno: employment period, reporting line, scope of responsibility, team management, awards and promotions

Step 3: Ask for missing information

Use the AskUserQuestion tool to ask for all key missing fields at once (up to 4 questions).

Questions should be specific and clear, for example:

• "What are the quantitative results of this project? (e.g., improved accuracy by 30%, covered 200+ stores)"
• "Was your role independently responsible, leading, or cross-departmental driving? What was the coverage scope?"

Step 4: Update files

Update files in the following order:

4.1 Update timeline.md

• If filling in fields: remove the supplemented items from the "Fields to be supplemented" section
• If a new company is involved: add a new row in the table

4.2 Update experience/{company}/overview.md

• Update the material status assessment
• Mark the supplemented content

4.3 Update experience/{company}/core-projects.md

• Add new project entries, using the standard template format
• Or update the information of existing projects

4.4 Resume sync (optional)

• Update only when the user explicitly requests it or the project is particularly important materials/resume/base-resume.md

Step 5: Verify consistency

After the update is complete, call the /verify skill to check material completeness and consistency.

Report to the user:

• Which files were updated
• Verification results (whether there are new missing items or inconsistencies)

Project entry template

Follow the format of materials/resume/versioning-strategy.md :

### 项目名称

**一句话定位**：在[背景和压力]下，为了[业务目标]，[搭建/优化]了[机制/系统/模型]

**我的角色**：[独立负责/主导/跨部门推动]，范围：[全司/200+ 门店/100+ 用户等具体范围]

**关键动作**：
- [统一口径/权限流程/模型框架/机制闭环/系统落地相关的动作]
- [动作 2]
- [动作 3]

**量化结果**：
- [准确率/效率/覆盖率/周期/成本/经营改善等量化指标]
- [结果 2]

**可迁移能力**：[预算预测/经营诊断/资本效率/组织机制/数字化等标签]

Edge case handling

New company not in timeline：

• First ask the user whether to add it to timeline.md
• Create the materials/experience/{company}/ directory
• Create overview.md and core-projects.md

Information conflict：

• If new information conflicts with existing information, show the differences
• Ask the user which version to keep

Missing experience directory：

• Automatically create the directory and basic files
• Initialize using the standard template

Resume sync judgment：

• By default, do not automatically sync to the resume
• Sync only when the user explicitly requests it
• Or ask whether to sync when the project has significant quantified results

Writing principles

Follow the core principles of the material library:

• Prioritize writing "business problem → mechanism/system → result"
• Write less of a laundry list of responsibilities, and more of "what was changed"
• When there are no hard results, write the coverage scope, process changes, and mechanism changes