菜单
Use when coordinating an end-to-end research competition or benchmark program across multiple lifecycle stages such as rules, data, baseline, experiments, claims, and submission; use a stage owner directly for isolated work.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Use when a user message needs Chinese-first intent inference, low-confidence collaborative clarification, routing, workflow weight control, skill choice, review/testing/planning/debugging/evaluation routing, proactive multi-thread collaboration or conflict coordination, continuation handling, execution permission inference, or protection from process over-escalation.
Use when active development or explicit refactoring has concrete code-structure risk: a source file is accumulating independently changing responsibilities, a class/component/function is hard to navigate or test, repeated changes touch distant sections, or the user asks to split a giant file; do not use for line count alone, generated/vendor/migration/schema/fixture files, or cohesive modules that remain easier to maintain together.
Use when the user explicitly enables an automated same-project multi-thread development loop that keeps peer Codex tasks progressing, recovers conflicts or stale coordination, integrates verified work into local main, and closes cleanup without repeated gates; do not use before opt-in, for one-off coordination, remote publication without permission, or subagent creation.
Use when existing independent Codex App threads work in the same project and need peer advice, collaboration proposals, shared progress awareness, ownership arbitration, conflict pause/resume, discussion, merge coordination, status exchange, or handoff through native thread tools without creating subagents.
Use when a verified or integrated software change has concrete temporary artifacts, generated noise, stale claims, merged local branches, or disposable worktrees to clean, or when the user explicitly asks to remove development residue or old branches.
Use when the user or project rules explicitly request project-local memory/dashboard initialization or updates, or when an existing `.docs/project-memory/` is needed for cross-session recovery, durable decisions, blockers, parallel-agent coordination, or formal handoff; do not auto-initialize or sync it for ordinary development.
| name | ccdawn-competition-research-lifecycle |
| description | Use when coordinating an end-to-end research competition or benchmark program across multiple lifecycle stages such as rules, data, baseline, experiments, claims, and submission; use a stage owner directly for isolated work. |
| license | MIT |
维护竞赛/benchmark 项目的阶段边界、事实源和跨阶段依赖，让当前最具体 owner 连续推进。它是全项目协调层，不重复执行研究、score、写作或工程流程。
ccdawn-ai-research-loop、ccdawn-score-loop、ccdawn-research-rigor-review、工程 owner、ccdawn-brt 或 BLOCKED。ccdawn-brt 或更具体 owner，复合任务不吞其他 owner。下一步建议: <一个具体动作>。只有请求跨越至少两个阶段，或规则、数据、baseline、claim、submission 之间的依赖需要统一治理时进入。单次论文复现/消融用 AI Research，反复 metric 晋升用 Score Loop，关键 claim 审查用 Rigor Review，具体工程故障用对应工程 owner。
按项目实际情况映射，不强制创建八套 artifact：规则与目标 -> 数据/协议 -> baseline -> 研究实验 -> 证据综合/claim -> 提交或发布。
每次只维护：当前阶段、active truth、阻塞下一阶段的最小缺口、primary owner、完成证据。已有项目工件优先；缺少模板但不影响当前决策时继续，不为形式补文档。
Smoke/proxy 只用于可运行性、淘汰和排序，不替代正式目标评估。外部 leaderboard 是重要校准证据，但不能静默改变本地 protocol 或 claim 范围。
阶段: <当前阶段>
- Active truth: <规则/数据/baseline/evidence>
- 关键缺口或漂移: <仅真实项>
- Primary owner 与产出:
- 阶段完成证据:
下一步建议: <一个具体动作>
跨会话或正式交接时才读取 REFERENCE.md、TEMPLATES.md 或维护持久阶段 artifact；普通推进不输出完整 lifecycle 表、BRT gate 或阶段菜单。