| name | survey-seed-harvest |
| description | Identify survey/review papers in a retrieved set and extract taxonomy seeds into `outline/taxonomy.yml` (topics/subtopics/terminology).
**Trigger**: survey seed harvest, taxonomy seeds, 从 survey 提 taxonomy, bootstrap taxonomy.
**Use when**: retrieval/dedup 后想快速从已有 survey/review 论文中提取术语与主题结构,用于加速 `taxonomy-builder`。
|
Survey Seed Harvest
Bootstrap taxonomy seeds from existing survey/review papers inside your retrieved set.
This is an accelerator for the early structure stage: it should make taxonomy-builder easier, not replace it.
Inputs
papers/papers_dedup.jsonl (deduped paper metadata with titles/abstracts)
Outputs
outline/taxonomy.yml (seed taxonomy; expected to be refined)
Workflow (heuristic)
Uses: papers/papers_dedup.jsonl.
- Find likely survey/review papers:
- title/abstract contains “survey”, “review”, “systematic”, “meta-analysis”
- Extract candidate topic terms and group them into:
- ~4–10 top-level nodes (“chapters”)
- 2–6 children per node (mappable leaves)
- Write short, actionable descriptions:
- what belongs here / what does not
- (optional) list 2–5 representative titles as seeds
- Treat the result as a starting point:
- pass it to
taxonomy-builder for domain-meaningful rewriting and scope alignment.
Quality checklist
Script (optional helper)
Quick Start
uv run python .codex/skills/survey-seed-harvest/scripts/run.py --help
uv run python .codex/skills/survey-seed-harvest/scripts/run.py --workspace <workspace>
All Options
--top-k <n>: number of candidate terms to consider
--min-freq <n>: minimum frequency threshold
Examples
- More conservative term selection:
uv run python .codex/skills/survey-seed-harvest/scripts/run.py --workspace <workspace> --top-k 80 --min-freq 3
Notes
- This helper is keyword-based; treat the output as seeds and refine with
taxonomy-builder.
Troubleshooting
Issue: no survey/review papers are detected in the set
Fix:
- Broaden retrieval (add “survey”, “review”, “benchmark” variants) or manually seed a few known surveys, then rerun.
Issue: taxonomy seeds look like generic buckets
Fix:
- Keep seeds concrete (named methods/benchmarks/tasks) and rely on
taxonomy-builder to rewrite under the actual scope.