krypton-planning

Krypton Planning

Krypton Planning 会将请求转化为目标包，在编写代码之前明确预期结果、事实责任方、契约、切换和验收证据。

核心规则

不要把任务列表当作计划。只有回答了以下问题，Krypton 计划才算准备就绪：

What outcome are we serving?
What current behavior is being replaced, redirected, deleted, or demoted?
Who owns the truth?
What contract crosses the boundary?
What is the smallest high-value slice?
What proves the result from the target person's perspective?
What kill criteria stop duplicate paths from living forever?

如果责任归属、切换、契约或证据不明确，请停止并先梳理，再制定计划。

工作流

1. 编写结果契约：

Plan title:
Intent:
Current behavior:
Expected outcome:
Target-perspective output:
Truth owner:
Contract boundary:
Cutover:
Displaced path:
Value density:
Evidence gate:
Acceptance evidence:
Evidence lane:
Kill criteria:
Non-goals:
Risk if wrong:

2. 在列出任务之前梳理架构切片：

Files to create:
Files to modify:
Files to avoid:
Source of truth:
Read path:
Write path:
Contract boundary:
Integration points:
Migration/cutover:
Displaced path:
Acceptance evidence gate:

对于范围较大或不明确的代码仓库，如果运行环境支持 Agent，请安排一名只读探索者。提出一个范围明确的问题，例如“梳理事实来源、读写路径、不安全文件和证据关卡”。执行会话应使用这份梳理结果，而不是重新探索同一个切片。

3. 除非用户指定其他位置，否则保存目标包：

docs/goals/<goal-slug>/PLAN.md
docs/goals/<goal-slug>/GOAL.md
docs/goals/<goal-slug>/EVIDENCE.md

PLAN.md 包含完整计划。GOAL.md 是简短的执行提示词，指向计划而不是复制计划。EVIDENCE.md 初始为空，并在执行期间填入从目标视角捕获的实际证明。

4. 按以下格式开始编写 PLAN.md 的头部：

# [Outcome Title] Implementation Plan

**Intent:** ...
**Current Behavior:** ...
**Expected Outcome:** ...
**Target-Perspective Output:** ...
**Truth Owner:** ...
**Contract Boundary:** ...
**Cutover:** ...
**Displaced Path:** ...
**Value Density:** ...
**Evidence Gate:** ...
**Acceptance Evidence:** ...
**Evidence Lane:** ...
**Kill Criteria:** ...
**Architecture Slice:** ...
**Plan Review Gate:** Requires PRE review before execution.

5. 将工作拆分为小任务。每项任务都要注明具体文件、允许的范围、预期输出、验证命令、验收证据，以及是否可以并行执行。

6. 尽可能进行 PRE 计划审查。使用 plan-reviewer-prompt.md 作为单项提示词模板。修复阻塞性问题或明确征得用户同意之前，不要执行。

GOAL.md 格式

使用这份精简的交接内容。操作人员应将其作为 /goal 提示词或下一会话的提示词粘贴到 Codex 或 Claude 中：

# Goal: [Outcome Title]

Use Krypton Execution to execute `docs/goals/<goal-slug>/PLAN.md`.

Core rules:
- Treat PLAN.md as the source plan.
- Preserve intent, ownership, contract, cutover, evidence, and kill criteria.
- Do not add a new dominant path without deleting, redirecting, demoting, or shimming the displaced path.
- Capture acceptance evidence from the target perspective and record it in EVIDENCE.md.
- Say "implemented but unproven" if that evidence cannot be captured.

EVIDENCE.md 格式

创建目标包时同时创建此文件，并在执行期间更新：

# [Outcome Title] Evidence

## Acceptance Evidence

Record the real artifact that proves the outcome from the target perspective.

## Verification

Record the focused check that passed, including the command and relevant output.

## Review Notes

Record reviewer, maintainer, or verifier findings that changed the result.