メニュー
Use when aligned requirements need a persistent or reviewable implementation plan, including a compact task graph only when independent deliverables, owners, dependencies, risk gates, or verification contracts make splitting valuable.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
| name | ccdawn-planning |
| description | Use when aligned requirements need a persistent or reviewable implementation plan, including a compact task graph only when independent deliverables, owners, dependencies, risk gates, or verification contracts make splitting valuable. |
| license | MIT |
把已对齐需求整理成最小可实施方案。规划/任务图只防具体风险；可直接实现并验证的任务留给当前 owner。
ccdawn-brt 或 BLOCKED。ccdawn-brt 或更具体 owner，复合任务不吞其他 owner。下一步建议: <一个具体动作>。只在规划 artifact 会被审阅、复用、交接或防止具体错误时进入本 skill，例如：
以下情况不进入：明确机械修改、单一 owning surface、低风险可逆修复、当前 owner 已能直接实施和验证。文件多不等于需要规划。
ccdawn-feature-reuse-research。PROFILE 才携带主指标、负载、baseline/测量和停止目标；FAST/CHECK 不增加性能章节。DIRECT_IMPLEMENTATION、COMPACT_PLAN、TASK_GRAPH 或 BLOCKED；不要再增加一个仅重复拆分判定的流程阶段。默认 DIRECT_IMPLEMENTATION；需要持久方案但无需真实拆分时使用 COMPACT_PLAN。满足以下条件即可由当前 owner 连续实施和验证：
只有任一条件成立才在当前方案内使用 TASK_GRAPH：
多个文件、较长描述、同机制机械替换、需要测试或普通跨模块修改，本身不触发拆分。NO_SPLIT 是 BRT/Planning 的内部结论，不需要独立 skill 来证明无需拆分。
任务图与实施方案一次完成：
SIMPLE 或 BDD_TDD。只有确定性行为存在重大回归、状态、数据、权限、迁移或公共契约风险时才使用 ccdawn-bdd-tdd-development。ccdawn-score-loop；metric 未提升不等于 TDD RED。紧凑任务卡只保留会被执行者消费的字段：
Task N: <可观察产出>
- Owner/Boundary:
- Dependency:
- Mode: SIMPLE / BDD_TDD
- Verification/Stop:
默认使用紧凑方案：
实施方案:
- 目标与范围:
- 推荐路径:
- 影响面与保护边界:
- 关键顺序/依赖:
- 风险决策:
- 验证与成功证据:
- 模式: DIRECT_IMPLEMENTATION / COMPACT_PLAN / TASK_GRAPH / BLOCKED
- 路由原因:
下一步建议: <由当前 owner 直接连续实施，或处理阻塞>
TASK_GRAPH 时在紧凑方案后追加拆分理由、Critical Path、并行/串行边界和必要任务卡，不重复目标、风险或验证章节。
只有跨会话、正式审阅或高风险方案才增加：备选路径、复用决策、假设、回滚、详细影响面和 ledger 增量。不要输出“无新增影响面”“无真实缺口”等占位式自审字段。
权限、安全、删除、迁移、发布、公共 API 或难回滚变更必须明确：受影响对象、兼容/迁移策略、失败检测、回滚路径和授权闸门。只有这些证据仍有缺口时才读取 plan-document-reviewer-prompt.md 做专项审查。
用户原始目标包含“修复/添加/实现/优化/继续”等执行许可且没有自然闸门时，方案完成后直接按推荐路由推进，不再次询问是否进入下一阶段。
只有跨会话、正式交接、Deferred 项或高风险决策需要持久状态时才更新 Workflow Ledger；普通规划把必要上下文放进紧凑方案即可。
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.