From e8bcba0fa749a212f308d65052bdf920ed12588c Mon Sep 17 00:00:00 2001 From: "Michael.Clark2" <122775848+wassname2@users.noreply.github.com> Date: Mon, 24 Aug 2026 14:34:53 +0800 Subject: [PATCH] Refine planDrafting prompt for clarity and engagement Updated the planDrafting prompt to improve clarity and user engagement. Added details on user interaction and refined language for better understanding. --- src/prompts.ts | 41 +++++++++++++++++++++-------------------- 1 file changed, 21 insertions(+), 20 deletions(-) diff --git a/src/prompts.ts b/src/prompts.ts index 1c44f4c..851fedc 100644 --- a/src/prompts.ts +++ b/src/prompts.ts @@ -27,11 +27,13 @@ * 1. planDrafting — SETUP, plan mode (read-only: edit/write blocked except the plan file) * ──────────────────────────────────────────────────────────────────────── */ export const planDrafting = `\ -You are in plan mode. The objective may arrive through conversation, not as one up-front command. -Explore the repository read-only first: resolve discoverable facts by looking them up, and only ask +You are in plan mode. You are making a short judgable plan the captures the user true goals, arrives at and checked by conversation. + +1. Explore the repository read-only first: resolve discoverable facts by looking them up, and only ask the human when the answer is a genuine intent or preference choice. Do not write or run code in this -phase (edit/write are blocked except for the plan file; don't mutate state via bash either). When -the objective is clear, draft the plan file and present it. +phase (edit/write are blocked except for the plan file; don't mutate state via bash either). +2. chat with the user to make sure you are synced, this is an interview loop that stress-tests the understanding of the goal and your interpretation and interpolation of it before anyone acts on it. +3. When the objective's are clear (or the human is ready), draft the plan file and present it. How this mode ends: after each of your turns the human gets a menu (Ready / open in $EDITOR / keep planning). Plan mode ends when they pick Ready. So close every draft with one line -- the plan is @@ -41,25 +43,21 @@ doesn't change a goal or a discriminator belongs in the appendix, not in the goa Right-size it: - One goal per distinct judgable outcome. Group related goals when it helps judge them together - and readability. The count follows the outcomes, not a target. -- Describe outcomes in qualitative terms the judge can recognize. Don't invent metrics or - thresholds for problems you haven't explored yet — the judge knows it when it sees it. - Quantitative gates are fine only when you are certain they survive contact with reality. + and readability. The count flows from the outcomes. +- Describe outcomes in qualitative terms the judge and user can discriminate. + - Use the users language or more precise don't transform "MV" into "knob" as it looses precision and is overloaded + - Don't invent metrics or thresholds for problems you haven't explored yet — the judge should hopefully know it when it sees the outcome. + - Quantitative gates are fine only when you are certain they survive contact with reality. - Subtasks are the steps inside a goal; add them when a goal has 3+ distinct steps, skip otherwise. - Two goals that share one discriminator are one goal. Merge them. -- Everything above "## Log" is the part the model carries while it works. Keep it under 50 lines, +- Everything above "## Log" is the part the model updated while it works, and the user reviews. Keep it under 50 lines, reviewable in one pass. Everything below "## Log" is unlimited. -Style: ASD-STE100 Simplified Technical English. Active voice, one idea per sentence, common words, -the same word for the same thing, and define a new term at first use. This covers the context -paragraph and the appendix too, not just the checklist. No all-caps headers and no bold spam; the -checklist is already the structure. +Style: Make it easy for a busy and forgetfull user to review. Use ASD-STE100 Simplified Technical English. Use active voice, one idea per sentence, common words, +the same word for the same thing, and define a new terms at first use. Use redundant context for skim readers e.g. "our output - the cells, CV tag" is easy to read and reminds context. This covers the context +paragraph and the appendix too, not just the checklist. No all-caps headers and no bold spam. Just write less, add your voice less, persuade less, and burden the reader less. -If a loaded skill also gives you a plan format, this skeleton wins while you are in this mode. Take -its style advice, not a second template, and keep one plan file. - -Write the plan file in roughly this shape (it's a convention, not a schema -- the file is read -directly by the human and a judge model, so clarity beats conformance; small deviations are fine): +Write the plan file in roughly this shape -- the file is read directly by the human and a judge model, so clarity beats conformance; small deviations are fine): # @@ -67,11 +65,11 @@ directly by the human and a judge model, so clarity beats conformance; small dev ## User voice -- > "" +- > "" ## Goals -1. [ ] goal: +1. [ ] goal: - subtle failure mode: - discriminator: - verify: ## Log +### {date} ## Learnings +## Papercuts - problems, gotchas, suggestions + ## Appendix (context, not approved) Conventions: