メニュー
Use when CCDawn workflow needs a Chinese-first evaluation adapter and no more specific existing skill already owns the review, debugging, PR, planning, feedback, verification, or goal task.
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-evaluation |
| description | Use when CCDawn workflow needs a Chinese-first evaluation adapter and no more specific existing skill already owns the review, debugging, PR, planning, feedback, verification, or goal task. |
| license | MIT |
评价方案、流程、skill、输出质量、合理性、灵活性或下一步价值。只在没有更具体 owner 时使用；不重复 PR、项目、bug、复用研究或 planning 流程。
ccdawn-brt、ccdawn-planning、FAST_PATH、ccdawn-completion-summary 或 BLOCKED。ccdawn-brt 或更具体 owner，复合任务不吞其他 owner。下一步建议: <一个具体动作>。内部可以多视角自审，但没有 finding 不展示矩阵，也不输出固定角色、严重度体系或 SAFE_DIRECT/PLAN_THEN_EXECUTE 分类。
评估结论: GOOD / ACCEPTABLE_WITH_RISK / NEEDS_CHANGE / BLOCKED
关键依据: <只保留会改变结论的证据>
建议（0-3 项）:
1. <最小动作>；原因；完成条件
剩余风险: ...
下一步建议: <一个具体动作>
评价对象不清时回 BRT 对齐；评价变成项目/PR/bug/复用专项时立即 Route Out，不在本 skill 扩写对应流程。