Agent skill

unit-planner

Instantiate or update a workspace `UNITS.csv` from a selected pipeline and units template (deps/checkpoints/acceptance). **Trigger**: unit planner, generate UNITS.csv, execution contract, units template, 生成工作单元. **Use when**: 初始化/更新执行合同：从 pipeline 选择生成 `UNITS.csv`，或 scope 扩展需要新增 units/依赖。 **Skip if**: `UNITS.csv` 已正确反映当前 scope（无需重写）。 **Network**: none. **Guardrail**: 保持 CSV 合法；scope 增长时新增 units；只在满足验收后标 `DONE`。

View SKILL.md on GitHub Repository
Stars 377
Forks 25

Install this agent skill to your Project

npx add-skill https://github.com/WILLOSCAR/research-units-pipeline-skills/tree/main/.codex/skills/unit-planner

SKILL.md

Skill: unit-planner

Goal

  • Turn a pipeline (pipelines/*.pipeline.md) into a concrete UNITS.csv contract for a specific workspace.

Inputs

  • PIPELINE.lock.md (preferred) or a chosen pipelines/*.pipeline.md
  • templates/UNITS.*.csv referenced by the pipeline front matter
  • Existing workspace artifacts (to adjust scope if needed)

Outputs

  • UNITS.csv (in the workspace root)
  • Optional: STATUS.md updated with next runnable units

Procedure (MUST FOLLOW)

Uses: templates/UNITS.*.csv.

  1. Read PIPELINE.lock.md (or ask to create it via pipeline-router).
  2. Copy the pipeline’s units_template into the workspace as UNITS.csv if missing.
  3. If UNITS.csv exists, only edit it to reflect:
    • new scope (add rows)
    • corrected dependencies
    • clarified acceptance criteria
  4. Ensure every unit has: unit_id, skill, outputs, acceptance, checkpoint, status, owner.
  5. Keep checkpoints consistent with CHECKPOINTS.md; add missing checkpoints if the pipeline uses custom checkpoints.

Acceptance criteria (MUST CHECK)

  • UNITS.csv parses as CSV and includes all required columns.
  • Every depends_on references an existing U###.

Side effects

  • Allowed: edit UNITS.csv, STATUS.md, CHECKPOINTS.md (for adding custom checkpoints).
  • Not allowed: change pipeline files in pipelines/ unless requested.

Troubleshooting

Issue: PIPELINE.lock.md is missing

Fix:

  • Run pipeline-router (Mode A) or python scripts/pipeline.py kickoff|init to create PIPELINE.lock.md before generating units.

Issue: UNITS.csv becomes invalid CSV after edits

Fix:

  • Keep semicolon-delimited inputs/outputs and avoid unescaped commas inside fields; validate with python scripts/validate_repo.py.

Recommended Agent Skills

Expand your agent's capabilities with these related and highly-rated skills.

WILLOSCAR/research-units-pipeline-skills

thesis-compile-review

对中文毕业论文进行编译、warning 分级、模板模式检查、数据与引用复查，并把问题回写成可继续迭代的 review checklist。 **Trigger**: 毕业论文编译检查, thesis compile review, warning 分级, 终稿复查, main.pdf 检查. **Use when**: 论文已经回写到 TeX 交付层，需要确认是否真正达到“可提交”的质量，而不是只做到能编译。 **Skip if**: 还处于中间层重构阶段，`chapters/*.tex` 尚未形成稳定交付稿。 **Network**: none. **Guardrail**: 不在这里重构章节主线；如果发现结构问题，明确回退到上游修复。

377 25
Explore
WILLOSCAR/research-units-pipeline-skills

front-matter-writer

Write the survey's front matter files (Abstract, Introduction, Related Work, Discussion, Conclusion) in paper voice, with high citation density and a single evidence-policy paragraph. **Trigger**: front matter writer, introduction writer, related work writer, abstract writer, discussion writer, conclusion writer, 引言, 相关工作, 摘要, 讨论, 结论. **Use when**: you are in C5 (prose allowed) and need the paper-like shell to stop the draft reading like stitched subsections. **Skip if**: `Approve C2` is missing in `DECISIONS.md`, or `citations/ref.bib` is missing. **Network**: none. **Guardrail**: no invented facts/citations; no pipeline jargon in final prose; no repeated evidence disclaimers; only use keys present in `citations/ref.bib`.

377 25
Explore
WILLOSCAR/research-units-pipeline-skills

thesis-question-list

维护中文毕业论文的 `codex_md/question_list.md`：把本轮问题、边界、优先级、协作方案和验收口径结构化，作为整条 thesis pipeline 的控制面。 **Trigger**: 毕业论文问题清单, thesis question list, 论文修改清单, 本轮目标, 结构问题梳理, review问题整理. **Use when**: 你已经有一批材料或上一轮 review 结果，需要明确这一轮到底修什么、不修什么，并给后续重构与编译复查提供统一入口。 **Skip if**: 当前只是在做一次性局部措辞修改，且没有形成新一轮结构/证据/编译问题。 **Network**: none. **Guardrail**: 不在这里写正文；不把问题单写成长篇散文；每条问题必须可执行、可验收。

377 25
Explore
WILLOSCAR/research-units-pipeline-skills

novelty-matrix

Create a novelty/prior-work matrix comparing the submission’s contributions against related work (overlaps vs deltas). **Trigger**: novelty matrix, prior-work matrix, overlap/delta, 相关工作对比, 新颖性矩阵. **Use when**: peer review 中评估 novelty/positioning，需要把贡献与相关工作逐项对齐并写出差异点证据。 **Skip if**: 缺少 claims（先跑 `claims-extractor`）或你不打算做新颖性定位分析。 **Network**: none (retrieval of additional related work is out-of-scope unless provided). **Guardrail**: 明确 overlap 与 delta；尽量给出可追溯证据来源（来自稿件/引用/作者陈述）。

377 25
Explore
WILLOSCAR/research-units-pipeline-skills

protocol-writer

Write a systematic review protocol into `output/PROTOCOL.md` (databases, queries, inclusion/exclusion, time window, extraction fields). **Trigger**: protocol, PRISMA, systematic review, inclusion/exclusion, 检索式, 纳入排除. **Use when**: systematic review pipeline 的起点（C1），需要先锁定 protocol 再开始 screening/extraction。 **Skip if**: 不是做 systematic review（或 protocol 已经锁定且不允许修改）。 **Network**: none. **Guardrail**: protocol 必须包含可执行的检索与筛选规则；需要 HUMAN 签字后才能进入 screening。

377 25
Explore
WILLOSCAR/research-units-pipeline-skills

rubric-writer

Write a rubric-based peer review report (`output/REVIEW.md`) using extracted claims and evidence gaps (novelty/soundness/clarity/impact). **Trigger**: rubric review, referee report, peer review write-up, 审稿报告, REVIEW.md. **Use when**: peer-review pipeline 的最后阶段（C3），已有 `output/CLAIMS.md` + `output/MISSING_EVIDENCE.md`（以及可选 novelty matrix）。 **Skip if**: 上游产物未就绪（claims/evidence gaps 缺失）或你不打算输出完整审稿报告。 **Network**: none. **Guardrail**: 给可执行建议（actionable feedback），并覆盖 novelty/soundness/clarity/impact；避免泛泛而谈。

377 25
Explore

Didn't find tool you were looking for?

Be as detailed as possible for better results