Back to Details

plan

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

Plan

计划

Create concrete plan files that 
plan-graph
can validate and turn into a DAG.
Use this skill after the product or technical direction is stable enough to break into implementation work. If the direction is still fuzzy, use 
grill-with-docs
or 
validate-direction
first.
创建具体的计划文件，供 
plan-graph
验证并转换为 DAG。
当产品或技术方向已足够稳定，可以拆分为实施工作时，使用此 skill。如果方向仍不清晰，请先使用 
grill-with-docs
或 
validate-direction
。

Output Location

输出位置

Write plans under:
text
.codex/plans/
Use one 
.plan.md
file for small work. Use multiple 
.plan.md
files when work has independent lanes, a clear dependency chain, or separate ownership boundaries.
将计划文件写入：
text
.codex/plans/
对于小型工作，使用一个 
.plan.md
文件。当工作包含独立的工作线、清晰的依赖链或不同的所有权边界时，使用多个 
.plan.md
文件。

Plan Shape

计划结构

Each plan file must use the 
plan-graph
frontmatter contract:
markdown
---
name: <short unique plan name>
overview: <one paragraph summary>
todos:
  - id: <stable-id>
    content: <concrete executable task>
    status: pending
isProject: false
---
每个计划文件必须遵循 
plan-graph
frontmatter 契约：
markdown
---
name: <short unique plan name>
overview: <one paragraph summary>
todos:
  - id: <stable-id>
    content: <concrete executable task>
    status: pending
isProject: false
---

<short unique plan name>

<short unique plan name>

Execution Notes

Execution Notes

<intent, context, accepted decisions, and useful references>
<intent, context, accepted decisions, and useful references>

Constraints

Constraints

<scope limits, compatibility requirements, files not to touch, rollout constraints>
<scope limits, compatibility requirements, files not to touch, rollout constraints>

Operator Guidance

Operator Guidance

<testing, sequencing, review notes, and when to use subagents>

Prefer stable kebab-case todo ids, for example `add-parser-tests`, `implement-parser`, `wire-cli`.
<testing, sequencing, review notes, and when to use subagents>

优先使用稳定的 kebab-case todo id，例如 `add-parser-tests`、`implement-parser`、`wire-cli`。

Workflow

工作流

  1. Read the PRD, issue, or brief.
  2. Read 
    CONTEXT.md
    , 
    docs/adr/
    , and 
    docs/agents/domain.md
    when present.
  3. Identify natural work lanes:
    • shared interface or schema work
    • independent implementation modules
    • tests and fixtures
    • migrations or compatibility work
    • documentation or rollout
  4. Choose one or more plan files.
  5. Make dependencies clear in plan structure:
    • sequential todos inside one plan for tightly coupled work
    • separate plan files for lanes that can run independently
    • note explicit inter-plan dependencies in 
      Operator Guidance
  6. Keep todo text executable and reviewable. Each todo should describe one outcome, not a vague phase.
  7. Validate with 
    plan-graph
    before any subagent launch.
  1. 阅读 PRD、issue 或简报。
  2. 如果存在，阅读 
    CONTEXT.md
    、
    docs/adr/
    和 
    docs/agents/domain.md
    。
  3. 识别自然划分的工作线：
    • 共享接口或 schema 工作
    • 独立实现模块
    • 测试与 fixtures
    • 迁移或兼容性工作
    • 文档或发布工作
  4. 选择一个或多个计划文件。
  5. 在计划结构中明确依赖关系：
    • 对于紧密耦合的工作，在同一个计划中使用顺序排列的 todos
    • 对于可以独立执行的工作线，使用独立的计划文件
    • 在 
      Operator Guidance
      中注明明确的计划间依赖
  6. 保持 todo 文本可执行且可审查。每个 todo 应描述一个明确结果，而不是模糊的阶段。
  7. 在启动任何 subagent 之前，先使用 
    plan-graph
    验证。

Boundaries

边界

  • Do not spawn subagents from this skill. Planning produces files; orchestration comes later.
  • Do not use a single huge plan when two independent lanes would graph cleanly.
  • Do not create speculative tasks for work the PRD explicitly excludes.
  • Do not mark todos 
    completed
    unless the work is already done in the repo.
  • 此 skill 不得启动 subagent。规划只负责生成文件；编排随后进行。
  • 当两个独立工作线能够清晰地形成图时，不要创建单个庞大的计划。
  • 不要为 PRD 明确排除的工作创建推测性任务。
  • 除非工作已在 repo 中完成，否则不要将 todo 标记为 
    completed
    。

Next Step

下一步

Run 
plan-graph validate
, then inspect the DAG or frontier. Use 
subagent-graph
only after the graph is valid and ownership boundaries are clear.
运行 
plan-graph validate
，然后检查 DAG 或 frontier。仅在图有效且所有权边界清晰后，才使用 
subagent-graph
。