domestic-acquisition

Domestic Acquisition Skills Package v1

Focused on customer acquisition and lead conversion in the Chinese mainland market, modular and acceptance-ready.

Package Structure

domestic-acquisition/
├── SKILL.md              ← 本文件（包索引 + 总览）
├── modules/              ← 子 skill 模块目录（逐个创建、逐个验收）
├── scripts/              ← 自动化脚本（跨模块复用）
├── templates/            ← 可复用模板
├── data/                 ← 静态数据/配置
└── references/           ← 参考资料

Module List

#	Module Name	Path	Status	Owner
1	Enterprise Lead Collection	modules/lead-mining/SKILL.md	✅ Accepted	Xiao data
2	Social Media Traffic Operations	modules/social-funnel/SKILL.md	⬜ To Be Created	Xiao content
3	Private Domain Conversion Scripts	modules/private-traffic/SKILL.md	⬜ To Be Created	Xiao content
4	Competitor Intelligence Monitoring	modules/competitor-intel/SKILL.md	⬜ To Be Created	Xiao research
5	Customer Profile Building	modules/customer-profile/SKILL.md	⬜ To Be Created	Xiao research
6	BD Outreach Automation	modules/outreach-automation/SKILL.md	⬜ To Be Created	Xiao market

Unified Skill Specification

Each submodule SKILL.md is created uniformly based on the template:

• Template path:templates/module-skill-template.md
• Principles: A single module solves only one problem; inputs/outputs/acceptance criteria must be quantifiable; dependencies must be explicitly stated.
• Status progression:待创建 → 草稿 → 可验收 → 已验收

Minimum required sections:

## 模块元信息
## 目标
## 触发条件
## 输入
## 执行步骤
## 输出
## 验收标准
## 依赖
## 失败处理

Among them, 模块元信息 permanently carries: status, owner, upstream input module, downstream output module, default output path. Used to unify structure, clarify boundaries, and facilitate acceptance one by one.

For the unified module boundary specification, see:references/module-boundaries.md。

Reading / Acceptance Order

Enter and accept uniformly in the following order to avoid structural drift:

1. First read this file to confirm the module list, status, and unified section requirements.
2. Then read references/module-boundaries.mdto confirm what the module is responsible for and not responsible for.
3. If the module involves structured leads, then read references/lead-record-schema.md, and do not invent field names.
4. When creating a new module, start from templates/module-skill-template.md , and do not copy and paste from old modules.
5. During acceptance, check item by item in the order of "structural completeness → boundary clarity → output reusability".

Iteration Log

Time	Increment	Status
2026-03-25 20:38	Initialize package structure + module list + unified specification	✅ Completed
2026-03-25 20:58	Add unified template for submodules templates/module-skill-template.md, and complete the goal/failure handling/status progression specification	✅ Completed
2026-03-25 21:16	Actually implement the modules/、scripts/、data/、references/ directory, and align the package structure with the index declaration	✅ Completed
2026-03-25 21:21	Create the first submodule modules/lead-mining/SKILL.md, complete the inputs/outputs/acceptance criteria, and advance it to acceptance-ready	✅ Completed
2026-03-25 21:26	Unify submodule metadata structure: template and lead-mining add "module metadata", fixing the status/owner/upstream-downstream/default output path fields	✅ Completed
2026-03-25 21:51	Complete the first acceptance loop for the first module lead-mining , advance status to "Accepted", and add acceptance records	✅ Done
2026-03-25 21:56	Extracted cross-module clue field specification references/lead-record-schema.md, and made lead-mining output explicit references, improving reusability	✅ Done
2026-03-25 22:14	Added package-level module boundary specification references/module-boundaries.md, and made the package index and lead-mining explicitly reference it, unifying the criteria for responsibility division	✅ Done
2026-03-25 22:24	Unified the boundary and field reuse hooks of the submodule template: the template references by default module-boundaries.md and lead-record-schema.md, reducing subsequent module structure drift	✅ Done