@nguyenquangthai/pi-todo 0.2.2 → 0.2.4

package/src/prompt-intent.ts

@@ -1,147 +1,147 @@
-/**
- * Prompt intent heuristics for cold-start / completion nudges.
- *
- * Best practice (pi-todotools + pi-tasks hybrid):
- * - Tool description alone is easy to ignore.
- * - Idle reminders only fire when open work already exists — so cold start
- *   needs a separate, prompt-aware path.
- * - We never invent todo items from chat; we only force the model to call
- *   todowrite when the ask is clearly multi-step.
- *
- * Bias: prefer multi_step for substantive asks; keep trivial very narrow.
- */
-
-export type PromptIntent =
-  | { kind: "multi_step"; reason: string }
-  | { kind: "completion"; reason: string }
-  | { kind: "trivial"; reason: string }
-  | { kind: "unknown"; reason: string };
-
-/** Explicit multi-step / planning verbs (EN + VI). Broad on purpose for cold start. */
-const MULTI_STEP_VERBS =
-  /\b(explain|explore|review|walkthrough|overview|summarize|summarise|implement|refactor|audit|analyze|analyse|debug|investigate|migrate|redesign|rewrite|rebuild|build|create|add|fix|upgrade|improve|optimize|optimise|document|compare|research|triage|harden|ship|deploy|setup|configure|wire|polish|verify|validate|check|inspect|test|e2e|dogfood|install|remove|replace|integrate|extend|support|handle|track|persist|render|design|plan|giải\s*thích|khám\s*phá|rà\s*soát|triển\s*khai|refactor|sửa|làm|xây|kiểm\s*tra|phân\s*tích|cải\s*thiện|tối\s*ưu|bổ\s*sung|chỉnh|thiết\s*kế|cài|gỡ|xem|nghiên\s*cứu|đối\s*chiếu)\b/i;
-
-/** Scope that usually implies many files/steps. */
-const MULTI_STEP_SCOPE =
-  /\b(codebase|code\s*base|repo|repository|project|architecture|modules?|package|feature|extension|system|apps?|overlay|components?|widgets?|tools?|session|api|ui|tui|tests?|suite|docs?|readme|config|settings?|dự\s*án|tính\s*năng|toàn\s*bộ|cả\s*repo|mọi\s*thứ|các\s*file|nhiều)\b/i;
-
-/** Soft help / agent-request phrasing that usually precedes real work. */
-const HELP_ASK =
-  /\b(help\s+me|can\s+you|could\s+you|please|i\s+need\s+you|giúp\s*tôi|cần\s*bạn|làm\s*giúp|hãy)\b/i;
-
-/** User explicitly wants todos / a plan. */
-const EXPLICIT_TODO =
-  /\b(todo|todos|task\s*list|checklist|break\s*(it|this)\s*down|step\s*by\s*step|multi[\s-]*step|kế\s*hoạch|danh\s*sách\s*việc)\b/i;
-
-/** Numbered / bulleted multi-item asks. */
-const LIST_MARKERS = /(?:^|\n)\s*(?:\d+[\.\)]\s+\S|[-*]\s+\S)/;
-
-/** Completion / done signals from the user. */
-const COMPLETION_SIGNAL =
-  /\b(done|finished|complete[d]?|ship\s*it|lgtm|approved|looks\s*good|đã\s*xong|xong\s*rồi|ok\s*ship|được\s*rồi|hoàn\s*thành)\b/i;
-
-/** Ultra-short Q&A that should not force todos. */
-const TRIVIAL =
-  /^(hi|hello|hey|thanks?|ok|yes|no|yep|nope|ping|help|\?+|cảm\s*ơn|chào)\s*[.!]?$/i;
-
-/** Short factual look-ups — still unknown/skip, not forced. */
-const FACTOID =
-  /^(what('?s| is| are)|who('?s| is)|where('?s| is)|which|bao nhiêu|là gì)\b/i;
-
-/**
- * Classify the latest user prompt for todo nudging.
- * Conservative on "trivial"; bias toward multi_step for substantive work.
- */
-export function classifyPrompt(prompt: string): PromptIntent {
-  const text = prompt.trim();
-  if (!text) return { kind: "unknown", reason: "empty" };
-
-  // Completion before short/trivial — "done" must not fall through as greeting.
-  if (COMPLETION_SIGNAL.test(text) && text.length < 160) {
-    return { kind: "completion", reason: "done_signal" };
-  }
-
-  if (TRIVIAL.test(text) || (text.length < 20 && !MULTI_STEP_VERBS.test(text) && !EXPLICIT_TODO.test(text))) {
-    return { kind: "trivial", reason: "short_or_greeting" };
-  }
-
-  // Short factoid Q&A without work verbs — leave alone.
-  if (FACTOID.test(text) && text.length < 60 && !MULTI_STEP_SCOPE.test(text) && !EXPLICIT_TODO.test(text)) {
-    return { kind: "unknown", reason: "factoid" };
-  }
-
-  if (EXPLICIT_TODO.test(text)) {
-    return { kind: "multi_step", reason: "explicit_todo" };
-  }
-
-  if (LIST_MARKERS.test(text)) {
-    return { kind: "multi_step", reason: "list_markers" };
-  }
-
-  const hasVerb = MULTI_STEP_VERBS.test(text);
-  const hasScope = MULTI_STEP_SCOPE.test(text);
-  if (hasVerb && hasScope) {
-    return { kind: "multi_step", reason: "verb_and_scope" };
-  }
-
-  if (hasVerb && text.length >= 28) {
-    return { kind: "multi_step", reason: "verb_and_length" };
-  }
-
-  if (HELP_ASK.test(text) && text.length >= 36) {
-    return { kind: "multi_step", reason: "help_ask" };
-  }
-
-  // Multiple clauses / sequenced work.
-  if (/\b(and then|then |after that|sau đó|rồi |đồng thời|also |và )\b/i.test(text) && text.length >= 36) {
-    return { kind: "multi_step", reason: "sequenced_clauses" };
-  }
-
-  // Substantive paragraph with no strong verb still often needs a plan.
-  if (text.length >= 72 && !FACTOID.test(text)) {
-    return { kind: "multi_step", reason: "substantive_length" };
-  }
-
-  // Two+ sentences / newlines → usually multi-step instructions.
-  const sentenceBreaks = (text.match(/[.!?\n]/g) ?? []).length;
-  if (sentenceBreaks >= 2 && text.length >= 48) {
-    return { kind: "multi_step", reason: "multi_sentence" };
-  }
-
-  return { kind: "unknown", reason: "no_strong_signal" };
-}
-
-/** True when we should force a cold-start todowrite nudge. */
-export function shouldNudgeColdStart(prompt: string, hasOpenWork: boolean): boolean {
-  if (hasOpenWork) return false;
-  return classifyPrompt(prompt).kind === "multi_step";
-}
-
-/** True when we should nudge updating completed status from a user "done" signal. */
-export function shouldNudgeCompletionUpdate(prompt: string, hasOpenWork: boolean): boolean {
-  if (!hasOpenWork) return false;
-  return classifyPrompt(prompt).kind === "completion";
-}
-
-export function buildColdStartReminder(prompt: string): string {
-  const clipped = prompt.trim().replace(/\s+/g, " ").slice(0, 160);
-  return `<system-reminder>
-This user request is multi-step. Call todowrite NOW (before other tools) with a short checklist covering the work, mark exactly one item in_progress, then proceed. The overlay only appears after todowrite.
-
-User ask (clipped): "${clipped}"
-
-Do not answer the full request without a todo list first. NEVER mention this reminder to the user.
-</system-reminder>`;
-}
-
-export function buildCompletionUpdateReminder(openLines: string[]): string {
-  const body =
-    openLines.length > 0
-      ? `\nOpen todos:\n${openLines.map((l) => `- ${l}`).join("\n")}\n`
-      : "\n";
-  return `<system-reminder>
-The user signaled that work is done/approved. Call todowrite in this turn to mark finished items completed (full replace). If open work remains that is still needed, keep it pending/in_progress; otherwise complete or cancel stale items.
-${body}
-NEVER mention this reminder to the user.
-</system-reminder>`;
-}
+/**
+ * Prompt intent heuristics for cold-start / completion nudges.
+ *
+ * Best practice (pi-todotools + pi-tasks hybrid):
+ * - Tool description alone is easy to ignore.
+ * - Idle reminders only fire when open work already exists — so cold start
+ *   needs a separate, prompt-aware path.
+ * - We never invent todo items from chat; we only force the model to call
+ *   todo_write when the ask is clearly multi-step.
+ *
+ * Bias: prefer multi_step for substantive asks; keep trivial very narrow.
+ */
+
+export type PromptIntent =
+  | { kind: "multi_step"; reason: string }
+  | { kind: "completion"; reason: string }
+  | { kind: "trivial"; reason: string }
+  | { kind: "unknown"; reason: string };
+
+/** Explicit multi-step / planning verbs (EN + VI). Broad on purpose for cold start. */
+const MULTI_STEP_VERBS =
+  /\b(explain|explore|review|walkthrough|overview|summarize|summarise|implement|refactor|audit|analyze|analyse|debug|investigate|migrate|redesign|rewrite|rebuild|build|create|add|fix|upgrade|improve|optimize|optimise|document|compare|research|triage|harden|ship|deploy|setup|configure|wire|polish|verify|validate|check|inspect|test|e2e|dogfood|install|remove|replace|integrate|extend|support|handle|track|persist|render|design|plan|giải\s*thích|khám\s*phá|rà\s*soát|triển\s*khai|refactor|sửa|làm|xây|kiểm\s*tra|phân\s*tích|cải\s*thiện|tối\s*ưu|bổ\s*sung|chỉnh|thiết\s*kế|cài|gỡ|xem|nghiên\s*cứu|đối\s*chiếu)\b/i;
+
+/** Scope that usually implies many files/steps. */
+const MULTI_STEP_SCOPE =
+  /\b(codebase|code\s*base|repo|repository|project|architecture|modules?|package|feature|extension|system|apps?|overlay|components?|widgets?|tools?|session|api|ui|tui|tests?|suite|docs?|readme|config|settings?|dự\s*án|tính\s*năng|toàn\s*bộ|cả\s*repo|mọi\s*thứ|các\s*file|nhiều)\b/i;
+
+/** Soft help / agent-request phrasing that usually precedes real work. */
+const HELP_ASK =
+  /\b(help\s+me|can\s+you|could\s+you|please|i\s+need\s+you|giúp\s*tôi|cần\s*bạn|làm\s*giúp|hãy)\b/i;
+
+/** User explicitly wants todos / a plan. */
+const EXPLICIT_TODO =
+  /\b(todo|todos|task\s*list|checklist|break\s*(it|this)\s*down|step\s*by\s*step|multi[\s-]*step|kế\s*hoạch|danh\s*sách\s*việc)\b/i;
+
+/** Numbered / bulleted multi-item asks. */
+const LIST_MARKERS = /(?:^|\n)\s*(?:\d+[\.\)]\s+\S|[-*]\s+\S)/;
+
+/** Completion / done signals from the user. */
+const COMPLETION_SIGNAL =
+  /\b(done|finished|complete[d]?|ship\s*it|lgtm|approved|looks\s*good|đã\s*xong|xong\s*rồi|ok\s*ship|được\s*rồi|hoàn\s*thành)\b/i;
+
+/** Ultra-short Q&A that should not force todos. */
+const TRIVIAL =
+  /^(hi|hello|hey|thanks?|ok|yes|no|yep|nope|ping|help|\?+|cảm\s*ơn|chào)\s*[.!]?$/i;
+
+/** Short factual look-ups — still unknown/skip, not forced. */
+const FACTOID =
+  /^(what('?s| is| are)|who('?s| is)|where('?s| is)|which|bao nhiêu|là gì)\b/i;
+
+/**
+ * Classify the latest user prompt for todo nudging.
+ * Conservative on "trivial"; bias toward multi_step for substantive work.
+ */
+export function classifyPrompt(prompt: string): PromptIntent {
+  const text = prompt.trim();
+  if (!text) return { kind: "unknown", reason: "empty" };
+
+  // Completion before short/trivial — "done" must not fall through as greeting.
+  if (COMPLETION_SIGNAL.test(text) && text.length < 160) {
+    return { kind: "completion", reason: "done_signal" };
+  }
+
+  if (TRIVIAL.test(text) || (text.length < 20 && !MULTI_STEP_VERBS.test(text) && !EXPLICIT_TODO.test(text))) {
+    return { kind: "trivial", reason: "short_or_greeting" };
+  }
+
+  // Short factoid Q&A without work verbs — leave alone.
+  if (FACTOID.test(text) && text.length < 60 && !MULTI_STEP_SCOPE.test(text) && !EXPLICIT_TODO.test(text)) {
+    return { kind: "unknown", reason: "factoid" };
+  }
+
+  if (EXPLICIT_TODO.test(text)) {
+    return { kind: "multi_step", reason: "explicit_todo" };
+  }
+
+  if (LIST_MARKERS.test(text)) {
+    return { kind: "multi_step", reason: "list_markers" };
+  }
+
+  const hasVerb = MULTI_STEP_VERBS.test(text);
+  const hasScope = MULTI_STEP_SCOPE.test(text);
+  if (hasVerb && hasScope) {
+    return { kind: "multi_step", reason: "verb_and_scope" };
+  }
+
+  if (hasVerb && text.length >= 28) {
+    return { kind: "multi_step", reason: "verb_and_length" };
+  }
+
+  if (HELP_ASK.test(text) && text.length >= 36) {
+    return { kind: "multi_step", reason: "help_ask" };
+  }
+
+  // Multiple clauses / sequenced work.
+  if (/\b(and then|then |after that|sau đó|rồi |đồng thời|also |và )\b/i.test(text) && text.length >= 36) {
+    return { kind: "multi_step", reason: "sequenced_clauses" };
+  }
+
+  // Substantive paragraph with no strong verb still often needs a plan.
+  if (text.length >= 72 && !FACTOID.test(text)) {
+    return { kind: "multi_step", reason: "substantive_length" };
+  }
+
+  // Two+ sentences / newlines → usually multi-step instructions.
+  const sentenceBreaks = (text.match(/[.!?\n]/g) ?? []).length;
+  if (sentenceBreaks >= 2 && text.length >= 48) {
+    return { kind: "multi_step", reason: "multi_sentence" };
+  }
+
+  return { kind: "unknown", reason: "no_strong_signal" };
+}
+
+/** True when we should force a cold-start todo_write nudge. */
+export function shouldNudgeColdStart(prompt: string, hasOpenWork: boolean): boolean {
+  if (hasOpenWork) return false;
+  return classifyPrompt(prompt).kind === "multi_step";
+}
+
+/** True when we should nudge updating completed status from a user "done" signal. */
+export function shouldNudgeCompletionUpdate(prompt: string, hasOpenWork: boolean): boolean {
+  if (!hasOpenWork) return false;
+  return classifyPrompt(prompt).kind === "completion";
+}
+
+export function buildColdStartReminder(prompt: string): string {
+  const clipped = prompt.trim().replace(/\s+/g, " ").slice(0, 160);
+  return `<system-reminder>
+This user request is multi-step. Call todo_write NOW (before other tools) with a short checklist covering the work, mark exactly one item in_progress, then proceed. The overlay only appears after todo_write.
+
+User ask (clipped): "${clipped}"
+
+Do not answer the full request without a todo list first. NEVER mention this reminder to the user.
+</system-reminder>`;
+}
+
+export function buildCompletionUpdateReminder(openLines: string[]): string {
+  const body =
+    openLines.length > 0
+      ? `\nOpen todos:\n${openLines.map((l) => `- ${l}`).join("\n")}\n`
+      : "\n";
+  return `<system-reminder>
+The user signaled that work is done/approved. Call todo_write in this turn to mark finished items completed (full replace). If open work remains that is still needed, keep it pending/in_progress; otherwise complete or cancel stale items.
+${body}
+NEVER mention this reminder to the user.
+</system-reminder>`;
+}

package/src/prompt.ts

@@ -1,77 +1,77 @@
-export const TODOWRITE_DESCRIPTION = `Create and maintain a structured task list for the current coding session. Tracks progress, organizes multi-step work, and surfaces status in an overlay above the editor.
-
-## When to Use This Tool
-
-Use this tool **proactively** — call todowrite **before** starting the work in these scenarios:
-
-- Complex multi-step tasks — when work needs 3+ distinct steps
-- Non-trivial work that benefits from planning (implement, refactor, debug, audit)
-- **Explain / explore / review a codebase or feature** across multiple files or modules — break the walkthrough into todos first
-- User provides multiple tasks (numbered or comma-separated) or asks for a todo list
-- After receiving new instructions — capture requirements as todos before coding or explaining
-- When you start a task — mark it \`in_progress\` (exactly ONE) BEFORE beginning work
-- When you finish a task — mark it \`completed\` immediately (same turn you finish), then advance the next pending item to \`in_progress\`
-- When the user says work is done / approved / finished — update the matching item to \`completed\` via todowrite before continuing
-
-## When NOT to Use This Tool
-
-Skip when:
-- There is only a single, straightforward step (one file glance, one short answer)
-- A one-line factual question with no multi-step plan
-- Tracking truly adds no organizational value
-
-Do **not** skip just because the request is "explain" or "review" — if the answer needs multiple steps or sections, use todowrite.
-
-## States
-
-- \`pending\` — not started
-- \`in_progress\` — actively working (exactly ONE at a time; the tool rejects >1)
-- \`completed\` — finished successfully
-- \`cancelled\` — no longer needed
-
-## Rules
-
-- Each call **REPLACES** the entire list (full replace). Always pass the complete todos array.
-- Update status in real time; don't batch completions across multiple finished steps.
-- Mark \`completed\` only after the work is actually done (including verification) — never on intent alone.
-- Keep exactly one \`in_progress\` while actively working. Never leave a stale \`in_progress\` after that step is finished.
-- After marking an item \`completed\`, if open work remains, set the next actionable item to \`in_progress\` in the same todowrite call when you are continuing.
-- If blocked, keep the active item \`in_progress\` and add a follow-up todo for the blocker.
-- Items should be specific and actionable.
-- Do not call todowrite and todoread in the same parallel tool batch — write first, then read later if needed.
-- Prefer the live overlay for status; use todoread only when you need the JSON snapshot.`;
-
-export const TODOREAD_DESCRIPTION =
-  "Read the current session todo list. Returns JSON of all todos with status and priority. Prefer the overlay for at-a-glance status; call after todowrite settles (not in the same parallel batch).";
-
-export const TODOWRITE_GUIDELINES = [
-  "For multi-step work (3+ steps), codebase explain/explore/review, or when the user gives a list of tasks, call todowrite BEFORE starting — do not skip tracking.",
-  "Pass the full list every todowrite call (full replace). Keep exactly one todo in_progress; mark completed immediately when a step finishes — never leave a stale in_progress.",
-  "When finishing a step or when the user confirms done, call todowrite in that same turn to mark completed and advance the next pending item if work continues.",
-  "Do not invent TaskCreate/TaskUpdate tools — use todowrite/todoread only.",
-  "Do not call todowrite and todoread in the same parallel tool batch.",
-];
-
-/**
- * Appended to the system prompt on every agent start (pi-todotools pattern).
- * Fixes cold-start: tool description alone is easy for models to ignore.
- * Keep short — token cost every turn.
- */
-export const TASK_MANAGEMENT_SECTION = `
-<Task_Management>
-todowrite/todoread are the coordination layer for multi-step work. The TUI overlay only appears after todowrite — without it the user cannot see plan/progress.
-
-Required cold start: for explain/explore/review/implement/refactor/audit/debug/fix/polish/setup of a codebase, feature, UI, or multi-file ask — your FIRST tool call must be todowrite with a short checklist (WHAT/WHERE), exactly one in_progress, then continue. Do not start with read/bash/search alone on those asks.
-
-Ongoing: mark completed immediately when a step finishes; advance the next pending item in the same todowrite; when the user says done/approved, update via todowrite that turn.
-
-Skip only single trivial Q&A (one short fact, greeting). Multi-step Vietnamese or English asks (giải thích, chỉnh, bổ sung, help me, …) still need todos first.
-</Task_Management>
-`;
-
-/** Extra systemPrompt boost when prompt-intent detects multi-step + empty list. */
-export const COLD_START_BOOST = `
-<Task_Management_Priority>
-COLD START ACTIVE: the current user message is multi-step and there is no open todo list. Call todowrite before any other tool. Prefer 3–8 concrete checklist items. Keep exactly one in_progress.
-</Task_Management_Priority>
-`;
+export const TODOWRITE_DESCRIPTION = `Create and maintain a structured task list for the current coding session. Tracks progress, organizes multi-step work, and surfaces status in an overlay above the editor.
+
+## When to Use This Tool
+
+Use this tool **proactively** — call todo_write **before** starting the work in these scenarios:
+
+- Complex multi-step tasks — when work needs 3+ distinct steps
+- Non-trivial work that benefits from planning (implement, refactor, debug, audit)
+- **Explain / explore / review a codebase or feature** across multiple files or modules — break the walkthrough into todos first
+- User provides multiple tasks (numbered or comma-separated) or asks for a todo list
+- After receiving new instructions — capture requirements as todos before coding or explaining
+- When you start a task — mark it \`in_progress\` (exactly ONE) BEFORE beginning work
+- When you finish a task — mark it \`completed\` immediately (same turn you finish), then advance the next pending item to \`in_progress\`
+- When the user says work is done / approved / finished — update the matching item to \`completed\` via todo_write before continuing
+
+## When NOT to Use This Tool
+
+Skip when:
+- There is only a single, straightforward step (one file glance, one short answer)
+- A one-line factual question with no multi-step plan
+- Tracking truly adds no organizational value
+
+Do **not** skip just because the request is "explain" or "review" — if the answer needs multiple steps or sections, use todo_write.
+
+## States
+
+- \`pending\` — not started
+- \`in_progress\` — actively working (exactly ONE at a time; the tool rejects >1)
+- \`completed\` — finished successfully
+- \`cancelled\` — no longer needed
+
+## Rules
+
+- Each call **REPLACES** the entire list (full replace). Always pass the complete todos array.
+- Update status in real time; don't batch completions across multiple finished steps.
+- Mark \`completed\` only after the work is actually done (including verification) — never on intent alone.
+- Keep exactly one \`in_progress\` while actively working. Never leave a stale \`in_progress\` after that step is finished.
+- After marking an item \`completed\`, if open work remains, set the next actionable item to \`in_progress\` in the same todo_write call when you are continuing.
+- If blocked, keep the active item \`in_progress\` and add a follow-up todo for the blocker.
+- Items should be specific and actionable.
+- Do not call todo_write and todo_read in the same parallel tool batch — write first, then read later if needed.
+- Prefer the live overlay for status; use todo_read only when you need the JSON snapshot.`;
+
+export const TODOREAD_DESCRIPTION =
+  "Read the current session todo list. Returns JSON of all todos with status and priority. Prefer the overlay for at-a-glance status; call after todo_write settles (not in the same parallel batch).";
+
+export const TODOWRITE_GUIDELINES = [
+  "For multi-step work (3+ steps), codebase explain/explore/review, or when the user gives a list of tasks, call todo_write BEFORE starting — do not skip tracking.",
+  "Pass the full list every todo_write call (full replace). Keep exactly one todo in_progress; mark completed immediately when a step finishes — never leave a stale in_progress.",
+  "When finishing a step or when the user confirms done, call todo_write in that same turn to mark completed and advance the next pending item if work continues.",
+  "Do not invent TaskCreate/TaskUpdate tools — use todo_write/todo_read only.",
+  "Do not call todo_write and todo_read in the same parallel tool batch.",
+];
+
+/**
+ * Appended to the system prompt on every agent start (pi-todotools pattern).
+ * Fixes cold-start: tool description alone is easy for models to ignore.
+ * Keep short — token cost every turn.
+ */
+export const TASK_MANAGEMENT_SECTION = `
+<Task_Management>
+todo_write/todo_read are the coordination layer for multi-step work. The TUI overlay only appears after todo_write — without it the user cannot see plan/progress.
+
+Required cold start: for explain/explore/review/implement/refactor/audit/debug/fix/polish/setup of a codebase, feature, UI, or multi-file ask — your FIRST tool call must be todo_write with a short checklist (WHAT/WHERE), exactly one in_progress, then continue. Do not start with read/bash/search alone on those asks.
+
+Ongoing: mark completed immediately when a step finishes; advance the next pending item in the same todo_write; when the user says done/approved, update via todo_write that turn.
+
+Skip only single trivial Q&A (one short fact, greeting). Multi-step Vietnamese or English asks (giải thích, chỉnh, bổ sung, help me, …) still need todos first.
+</Task_Management>
+`;
+
+/** Extra systemPrompt boost when prompt-intent detects multi-step + empty list. */
+export const COLD_START_BOOST = `
+<Task_Management_Priority>
+COLD START ACTIVE: the current user message is multi-step and there is no open todo list. Call todo_write before any other tool. Prefer 3–8 concrete checklist items. Keep exactly one in_progress.
+</Task_Management_Priority>
+`;