You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: internal/promptasset/templates/context/plan_mode_build_execute.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -4,7 +4,7 @@ You are currently in build execution.
4
4
- If a current plan summary is attached, use it as guidance by default.
5
5
- If the summary is insufficient for the current task, consult the attached full plan view when available.
6
6
- If no current plan is attached, continue using task state, todos, and the conversation context.
7
-
- If no current plan and no Todo State are attached, create current-run required todos with `todo_write` before the first substantive tool call for project analysis, documentation writing, code changes, multi-step debugging, or verification work.
7
+
- If no Todo State is attached, create current-run required todos with `todo_write` before the first substantive tool call for project analysis, documentation writing, code changes, multi-step debugging, or verification work.
8
8
- Do not update or complete todo IDs that are not present in the current Todo State; create new current-run todos instead.
9
9
- Small necessary deviations are allowed, but explain why they are needed.
10
10
- Do not create or rewrite the current full plan in this stage.
Copy file name to clipboardExpand all lines: internal/promptasset/templates/context/plan_mode_plan.md
+4-6Lines changed: 4 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -6,9 +6,7 @@ You are currently in the planning stage.
6
6
-**If no Current Plan section is attached, your first priority is to produce a plan.** The user has entered planning mode expecting a structured plan. Research the codebase as needed, then output a complete `plan_spec` + `summary_candidate` JSON. Do not end the turn with only a conversational answer when there is no existing plan.
7
7
- If a Current Plan is already present, you may refine, replace, or discuss it. When the user asks a clarifying question or wants to explore options without committing to a new plan revision, you may answer conversationally without outputting planning JSON.
8
8
- Only output a JSON object containing `plan_spec` and `summary_candidate` when you are explicitly creating or rewriting the current full plan.
9
-
-`plan_spec` must include `goal`, `steps`, `constraints`, `todos`, and `open_questions`.
10
-
-`plan_spec.todos`**must not be empty**. Populate it with the major actionable items that the plan requires. Each todo must have a unique `id`, a descriptive `content`, and `status: "pending"`. Without todos the plan has no executable work items and the build stage cannot proceed.
11
-
-`summary_candidate` must include `goal`, `key_steps`, `constraints`, and `active_todo_ids`.
12
-
- If a Todo State section is attached, decide which non-terminal todos still belong to the current plan.
13
-
- Todos that still belong to the current plan must appear in `plan_spec.todos` and their IDs must appear in `summary_candidate.active_todo_ids`.
14
-
- Todos that do not belong to the current plan must not be copied into the new plan; create replacement plan-owned todos when ongoing work is still needed.
9
+
-`plan_spec` must include `goal`, `steps`, `constraints`, and `open_questions`.
10
+
-`plan_spec.todos` is optional legacy data. Do not create execution todos in plan mode; build mode will create and maintain runtime todos when implementation starts.
11
+
-`summary_candidate` must include `goal`, `key_steps`, and `constraints`.
12
+
- If a Todo State section is attached, treat it as build execution progress only. Do not copy, rewrite, or complete those todos while planning.
todo_bootstrap_required: This build run has no current plan and no active todos.
13
+
todo_bootstrap_required: This build run has no active todos.
14
14
15
15
Before project analysis, documentation writing, code changes, multi-step debugging, or verification work, call todo_write with action=plan or action=add to create required todos for this run.
16
16
17
+
If a Current Plan is attached, use it only as planning context. Create current-run execution todos explicitly instead of assuming plan steps already exist as todos.
18
+
17
19
Do not update or complete old todo IDs that are not present in the current Todo State.`
18
20
19
-
// maybeAppendTodoBootstrapReminder 在 direct build 缺少 plan/todo 时注入一次结构化提醒。
21
+
// maybeAppendTodoBootstrapReminder 在 build 缺少执行态 todo 时注入一次结构化提醒。
0 commit comments