plan-strata

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

Plan Strata

Keep project intent, execution, and evidence connected across sessions. A single execution plan can contain development and research tasks shared by several agents. Use the user's language for project documents.

在跨会话过程中保持项目意图、执行过程及相关证据的关联。一份执行计划可包含多个Agent共享的开发与研究任务。项目文档使用用户的语言编写。

Start or resume

启动或恢复

Inspect project instructions and existing planning files. Preserve the project's established locations and terminology. Read the protocol when creating records, selecting a revision, or using the validator.
For an existing task, recover its recorded plan binding and handoff. For new work, follow
```
plans/CURRENT.md
```
. If the pointer is missing or inconsistent, report the ambiguity and resolve it from explicit project/user context; version ordering and modification time do not select a plan.
Read the selected core, execution plan, progress, and the evidence needed for the next action. Inspect actual files and running jobs where relevant to reconcile an interrupted handoff. State the next bounded action.
For a new iteration, adapt the core, plan, progress, and pointer templates. Fill actual goals and acceptance criteria before selecting a ready plan. Use existing authorization for work already in scope. Escalate a change in overall goals, resources, or external effects when it needs new authority.

检查项目指令及现有规划文件。保留项目既定的存储位置和术语。在创建记录、选择修订版本或使用验证工具时，请阅读协议文档。
针对现有任务，恢复其已记录的计划绑定关系和交接信息。针对新工作，请遵循
```
plans/CURRENT.md
```
中的内容。若指针缺失或不一致，请报告该歧义问题，并从明确的项目/用户上下文信息中解决；版本排序和修改时间不能作为计划选择的依据。
阅读选定的核心文档、执行计划、进度信息，以及下一步操作所需的证据。必要时检查实际文件和运行中的任务，以协调中断的交接流程。明确说明下一步的限定性操作。
针对新迭代，请调整核心文档、计划模板、进度模板和指针模板。在选定可用计划前，填写实际目标和验收标准。对已在范围内的工作使用现有授权。当整体目标、资源或外部影响发生变更需要新授权时，需进行上报。

Execute and hand off

执行与交接

Put task definitions and dependencies in the plan; maintain live state only in progress. Record a plan path and content hash when starting a task. That binding survives later changes to CURRENT.
Keep one progress writer per iteration. Workers share the plan, own distinct tasks, and submit separate reports when concurrent execution needs them. Concurrent code writers also need an explicit integration method and isolated outputs; the skill does not supply a scheduler or a lock.
At a meaningful milestone, blocker, or handoff, record what changed, where the artifacts are, what was checked, what remains uncertain, and the next action. Record a running job's identifier and output location before yielding it. Single-agent work can keep this in progress; create
```
reports/
```
when needed.
For development tasks, read development guidance before defining acceptance or accepting a delivery. For research tasks, read research guidance before planning or interpreting evidence. Mixed plans use both; each task retains its own acceptance meaning.

将任务定义和依赖关系纳入计划；仅在进度文档中维护实时状态。启动任务时记录计划路径和内容哈希值。该绑定关系不受后续CURRENT文件变更的影响。
每个迭代仅保留一位进度记录者。工作人员共享计划，负责不同的任务，当需要并发执行时提交单独的报告。并发代码编写者还需明确集成方法和独立输出；本Skill不提供调度器或锁机制。
在重要里程碑、阻塞点或交接环节，记录变更内容、工件存储位置、已检查内容、仍存在的不确定性以及下一步操作。在移交运行中的任务前，记录其标识符和输出位置。单Agent工作可将这些信息记录在进度文档中；必要时创建
```
reports/
```
目录。
针对开发任务，在定义验收标准或接受交付前，请阅读开发指南。针对研究任务，在规划或解读证据前，请阅读研究指南。混合计划需同时遵循两者；每个任务保留其自身的验收定义。

Check and decide

检查与决策

Inspect the actual result using the plan's acceptance method. An execution report is a starting point for verification. Record a scoped conclusion in a new check, including the bound plan, inspected subjects, evidence, method, limitations, and next decision. Preserve earlier checks.
Mark a task
```
done
```
only when its applicable check passes and dependencies allow acceptance. A valid research activity can be done with an inconclusive or negative finding. Check integrated behavior separately when the plan requires it. Record review provenance; another agent is optional, not proof by itself.
For the bundled metadata format, run:
text
```
python3 <skill-directory>/scripts/strata.py validate --project <project-directory>
```
Fix inconsistent records. This read-only command verifies references, selected file hashes, and state consistency.
```
consistent
```
does not mean tests ran, evidence is truthful, or the research claim is established. Inspect
```
overall
```
separately. Existing alternative formats may be checked manually without migration; disclose that the bundled validator was not used on them.
Report the outcome, remaining limitations, and justified next action. Stop or replan when the agreed budget or decision boundary is reached.

使用计划中的验收方法检查实际结果。执行报告是验证工作的起点。在新的检查文档中记录限定范围的结论，包括绑定的计划、检查对象、证据、方法、局限性以及下一步决策。保留之前的检查记录。
仅当任务通过相应检查且依赖关系允许验收时，才可标记为
```
done
```
。有效的研究活动即使得出非结论性或负面结果，也可标记为完成。当计划要求时，需单独检查集成行为。记录审核来源；其他Agent参与并非验证的充分条件。
对于捆绑元数据格式，运行以下命令：
text
```
python3 <skill-directory>/scripts/strata.py validate --project <project-directory>
```
修复不一致的记录。此只读命令用于验证引用关系、选定的文件哈希值和状态一致性。“一致”并不意味着已运行测试、证据真实可信或研究结论成立。需单独检查
```
overall
```
内容。现有替代格式可手动检查，无需迁移；需说明未对其使用捆绑验证工具。
报告结果、剩余局限性以及合理的下一步操作。当达到约定的预算或决策边界时，停止工作或重新规划。

Revise

修订

Keep a round's identity (for example

P001

) separate from its revision. Add a new plan revision for changed scope, dependencies, methods, or acceptance criteria; update progress for ordinary execution. Change core when project intent or key constraints change. Read the protocol's revision rules before changing a selected baseline. Write the reason and affected tasks into the new plan.

Keep started revisions available with their exact bytes. Select the new ready revision explicitly, then reconcile pending work and previous acceptance. Running tasks retain their bindings until explicitly continued, stopped, or reassigned. Use a new check to justify reuse under changed criteria. Preserve historical results while marking current acceptance

needs_review

when applicability is uncertain.

将一轮迭代的标识（例如

P001

）与其修订版本区分开。当范围、依赖关系、方法或验收标准发生变更时，添加新的计划修订版本；日常执行更新则记录在进度文档中。当项目意图或关键约束发生变更时，更新核心文档。在修改选定基线前，请阅读协议文档中的修订规则。将修订原因和受影响的任务写入新计划。

保留已启动的修订版本及其确切内容。明确选定新的可用修订版本，然后协调待处理工作和之前的验收结果。运行中的任务在未被明确继续、停止或重新分配前，保留其绑定关系。若需在变更后的标准下复用任务，需通过新的检查来证明合理性。当适用性不确定时，在保留历史结果的同时，将当前验收状态标记为

needs_review

。