メニュー
Route an unbound research Goal to one Workflow or materialize its initial C0 kickoff block; use during initial binding, not for later checkpoint summaries or approval.
デフォルトでは、最初にソースを確認する Prompt が選択されています。直接コマンドに切り替えるか、ローカルコピーをダウンロードすることもできます。
インストールを決める前に、SKILL.md と SkillsMP に表示されている付属ファイルをお読みください。
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
直接コマンドでは確認用 Prompt が省略されます。実行前にソースを確認してください。
npx skills add https://github.com/WILLOSCAR/research-units-pipeline-skills --skill pipeline-routerコマンドは1行のまま表示されます。コピー前に横へスクロールして全体を確認してください。
ローカルで確認しますか？SkillsMP が現在取得できるファイルをダウンロードできます。
Create per-subsection evidence packs (NO PROSE): claim candidates, concrete comparisons, evaluation protocol, limitations, plus citation-backed evidence snippets with provenance. **Trigger**: evidence draft, evidence pack, claim candidates, concrete comparisons, evidence snippets, provenance, 证据草稿, 证据包, 可引用事实.
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, 引言, 相关工作, 摘要, 讨论, 结论.
Scaffold a LaTeX project (`latex/main.tex`, optional bibliography wiring, structure) from an existing Markdown draft. **Trigger**: latex scaffold, md→tex, LaTeX 项目骨架, 生成 main.tex. **Use when**: 需要 LaTeX/PDF 交付（例如 arxiv-survey-latex pipeline），且 draft 已生成/已进入写作阶段。
SKILL.md を表示中
SOC 職業分類に基づく
| name | pipeline-router |
| description | Route an unbound research Goal to one Workflow or materialize its initial C0 kickoff block; use during initial binding, not for later checkpoint summaries or approval. |
Routing is a commitment: select one Workflow from the desired Artifact and evidence method, record that choice, and expose the next human Decision.
GOAL.md, or the current user request when the Workspace is new.PIPELINE.lock.md, UNITS.csv, STATUS.md, and DECISIONS.md when
present.docs/PIPELINE_TAXONOMY.md and candidate Pipeline front matter during
selection.PIPELINE.lock.md for a newly bound Goal.DECISIONS.md.queries.md when the selected retrieval Workflow starts at C0.STATUS.md.Read the Goal and identify:
When a routing discriminator is missing, write the smallest grouped question
set to DECISIONS.md and stop at that Decision.
Completion criterion: every fact that can change the Workflow choice is known
or explicitly bounded in DECISIONS.md.
Load docs/PIPELINE_TAXONOMY.md, then inspect only the candidate Pipeline
contracts. Choose from target Artifact and evidence method rather than keyword
matching alone. Treat delivery profiles and course-report use cases as overlays
inside their existing Workflow family.
Completion criterion: exactly one executable Pipeline is selected and its target Artifacts match the Goal.
Write PIPELINE.lock.md with:
pipeline: <pipeline path>
units_template: <template path from Pipeline front matter>
locked_at: <YYYY-MM-DD>
Initialize UNITS.csv from that template when the Workspace is new. Preserve a
valid existing lock; a route change is an explicit operator Decision followed
by reinitialization or migration, never a silent rewrite.
Completion criterion: the lock, Unit template, and Workspace projection refer to the same Pipeline.
Materialize the C0 kickoff block and approval checkbox in DECISIONS.md. Seed
queries.md from the Goal when retrieval is part of the selected Workflow.
Later checkpoints use checkpoint-brief. Historical Workspaces whose saved
Unit still invokes pipeline-router after C0 are delegated to
checkpoint-brief with a deprecation warning; the router never approves them.
The deterministic helper may be used after selection:
uv run python .codex/skills/pipeline-router/scripts/run.py \
--workspace workspaces/<name> \
--checkpoint C0
Completion criterion: DECISIONS.md contains the C0 checkpoint and one
clear approval or answer surface; retrieval Workflows have a non-empty C0 query
seed.
Check that the locked Pipeline exists, its Unit template exists, and the active
checkpoint is represented in both STATUS.md and DECISIONS.md.
Completion criterion: the Pipeline Runner can continue from Workspace files without making another routing inference.
docs/PIPELINE_TAXONOMY.md only while selecting or deliberately changing
a Workflow.pipelines/*.pipeline.md is the execution
contract and the taxonomy leaves context.assets/pipeline-selection-form.md only when missing routing facts require
a human answer.--help when C0 materialization needs debugging; the
helper records the initial route projection but does not choose one.