メニュー
Use when the user explicitly requests an open-ended, persistent iteration policy with evidence-based next-step selection and stop conditions, and no domain-specific research, score, development, or coordination owner already controls the loop.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
| name | ccdawn-goal-loop |
| description | Use when the user explicitly requests an open-ended, persistent iteration policy with evidence-based next-step selection and stop conditions, and no domain-specific research, score, development, or coordination owner already controls the loop. |
| license | MIT |
为明确要求持续迭代的开放目标提供轻量控制策略。它不替代 BRT 对齐、专项 owner、Planning 或 Project Memory，也不用于普通有限任务。
ADVANCE / ITERATE / STOP / BLOCKED 和下一动作。ccdawn-brt 或 BLOCKED。ccdawn-brt 或更具体 owner，复合任务不吞其他 owner。下一步建议: <一个具体动作>。必须同时满足：用户明确要求持续/反复迭代；终点不能预先拆成有限任务；每轮需要根据证据选择下一动作；没有更具体 owner。普通“继续”“优化到完成”、有限实现、已知 task graph、实验/score/research loop 和多 Agent 协调均不触发。
Goal / Evidence / Constraints / Stop；BRT 已提供的内容直接继承，不重复询问或展示合同。ADVANCE，修正方法用 ITERATE，目标已达成或继续无价值用 STOP，缺不可约输入/权限用 BLOCKED。Goal Loop 是控制策略，不是状态存储。对话内续接使用 BRT Runtime；只有用户/项目已启用跨会话 memory 且当前决定值得持久化时，才由 ccdawn-dawn-agent-html-memory 写一次 durable delta。不得逐轮生成 ledger、dashboard、完整尝试历史或重复 goal contract。
普通轮次只给：本轮结果 / 新证据 / 决策 / 下一动作。只有 BLOCKED 才补已尝试的关键路径和一个不可约问题；只有用户明确要求正式交接时才路由 Completion Summary。
下一步建议: <一个具体动作>
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.