Agent skill
subsection-writer
Write survey prose into per-section files under `sections/` so each unit can be QA'd independently before merging. **Trigger**: subsection writer, per-section writing, split sections, sections/, 分小节写, 按章节拆分写作. **Use when**: `Approve C2` is recorded and writer packs exist (`outline/writer_context_packs.jsonl`); you want evidence-bounded drafting without a monolithic one-shot draft. **Skip if**: `DECISIONS.md` approval is missing, or `outline/evidence_drafts.jsonl` / `citations/ref.bib` is missing. **Network**: none. **Guardrail**: do not invent facts/citations; no TODO/ellipsis leakage; keep citations subsection- or chapter-scoped; H3 body files and chapter leads must not contain headings.
Install this agent skill to your Project
npx add-skill https://github.com/WILLOSCAR/research-units-pipeline-skills/tree/main/.codex/skills/subsection-writer
SKILL.md
Subsection Writer (compatibility router)
Purpose: write or refine per-section survey prose under sections/ while keeping the current pipeline contract unchanged.
Compatibility mode:
- output paths stay the same
scripts/run.pystill handles approval checks, missing-file bootstrap, andsections/sections_manifest.jsonl- writing guidance now lives in
references/instead of being encoded primarily in the script
Load Order
Always read:
references/overview.mdreferences/paragraph_jobs.mdreferences/paragraph_job_archetypes.mdwhen adjusting paragraph-role behavior or refactoring writer policy out of Pythonreferences/bootstrap_assembly.mdwhen reasoning about compatibility-mode bootstrap behavior
Read as needed:
references/opener_catalog.mdwhen paragraph 1 sounds generic or narratedreferences/contrast_moves.mdwhen building A-vs-B comparison paragraphsreferences/eval_anchor_patterns.mdwhen making performance / robustness / benchmark claimsreferences/limitation_moves.mdwhen adding caveats or local conclusionsreferences/examples_good.mdandreferences/examples_bad.mdfor calibration only
Machine-readable contract:
assets/subsection_writer_context.schema.jsonassets/bootstrap_paragraph_templates.jsonassets/paragraph_job_templates.json
Inputs
Required:
DECISIONS.md(must includeApprove C2)outline/outline.ymloutline/writer_context_packs.jsonl(preferred)citations/ref.bib
Optional but useful:
outline/subsection_briefs.jsonloutline/evidence_drafts.jsonloutline/evidence_bindings.jsonloutline/anchor_sheet.jsonloutline/chapter_briefs.jsonl
Outputs
Keep the current contract:
sections/abstract.mdsections/discussion.mdsections/conclusion.mdsections/S<sec_id>.mdfor H2-without-H3 bodiessections/S<sec_id>_lead.mdfor H2 lead blockssections/S<sub_id>.mdfor H3 bodiessections/sections_manifest.jsonl
Writer policy
The active rule is move coverage, not paragraph quota. A subsection should cover the necessary argument moves the pack supports; do not pad to a fixed count when the evidence does not justify it.
Opener / ending policy:
- generate 2-4 opener candidates from the pack's actual tension, contrast, protocol, or limitation signals; keep the most content-bearing option instead of reusing one stock stem everywhere
- let subsection endings emerge from evidence-bearing comparison / limitation material; do not append a fixed “safest synthesis / decision rule” closer just to make the paragraph feel finished
- normalize internal axis labels into natural reader prose; slash-style brief handles should remain planning metadata, not leak unchanged into the paper
Script boundary
Use scripts/run.py as a helper only:
- it may bootstrap missing H3 files and refresh the manifest
- it must not be treated as the canonical source of prose shape or voice policy
Quick Start
python .codex/skills/subsection-writer/scripts/run.py --workspace workspaces/<ws>
Troubleshooting
- If the pack is thin, stop and route upstream instead of padding prose.
- If the subsection sounds narrated, reload
references/opener_catalog.mdandreferences/examples_bad.md. - If a claim lacks protocol context, reload
references/eval_anchor_patterns.mdbefore rewriting.
Execution notes
When running in compatibility mode, scripts/run.py currently consumes:
DECISIONS.mdforApprove C2outline/outline.ymlto enumerate chapter / subsection filesoutline/writer_context_packs.jsonlas the primary drafting inputcitations/ref.bibfor in-scope citationsoutline/subsection_briefs.jsonl,outline/evidence_drafts.jsonl,outline/evidence_bindings.jsonl,outline/anchor_sheet.jsonl, andoutline/chapter_briefs.jsonlas optional enrichment sources
Script
Quick Start
python .codex/skills/subsection-writer/scripts/run.py --workspace <workspace_dir>
All Options
--workspace <dir>--unit-id <id>--inputs <a;b;...>--outputs <a;b;...>--checkpoint <C*>
Examples
python .codex/skills/subsection-writer/scripts/run.py --workspace workspaces/<ws>
Troubleshooting
- If
DECISIONS.mdlacksApprove C2, stop and fix approval first. - If
outline/writer_context_packs.jsonlis thin, reroute upstream instead of padding prose. - If citation scope looks wrong, re-check
citations/ref.biband the writer packs before editing output text.
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
thesis-compile-review
对中文毕业论文进行编译、warning 分级、模板模式检查、数据与引用复查,并把问题回写成可继续迭代的 review checklist。 **Trigger**: 毕业论文编译检查, thesis compile review, warning 分级, 终稿复查, main.pdf 检查. **Use when**: 论文已经回写到 TeX 交付层,需要确认是否真正达到“可提交”的质量,而不是只做到能编译。 **Skip if**: 还处于中间层重构阶段,`chapters/*.tex` 尚未形成稳定交付稿。 **Network**: none. **Guardrail**: 不在这里重构章节主线;如果发现结构问题,明确回退到上游修复。
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`.
thesis-question-list
维护中文毕业论文的 `codex_md/question_list.md`:把本轮问题、边界、优先级、协作方案和验收口径结构化,作为整条 thesis pipeline 的控制面。 **Trigger**: 毕业论文问题清单, thesis question list, 论文修改清单, 本轮目标, 结构问题梳理, review问题整理. **Use when**: 你已经有一批材料或上一轮 review 结果,需要明确这一轮到底修什么、不修什么,并给后续重构与编译复查提供统一入口。 **Skip if**: 当前只是在做一次性局部措辞修改,且没有形成新一轮结构/证据/编译问题。 **Network**: none. **Guardrail**: 不在这里写正文;不把问题单写成长篇散文;每条问题必须可执行、可验收。
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;尽量给出可追溯证据来源(来自稿件/引用/作者陈述)。
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。
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;避免泛泛而谈。
Didn't find tool you were looking for?