From 17b4304a5f89939c02a97674a286c225a009a9b8 Mon Sep 17 00:00:00 2001 From: YeonGyu-Kim Date: Wed, 17 Dec 2025 19:11:06 +0900 Subject: [PATCH] Expand Todo Management section with detailed guidelines MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit 🤖 GENERATED WITH ASSISTANCE OF [OhMyOpenCode](https://github.com/code-yeongyu/oh-my-opencode) --- src/agents/omo.ts | 41 +++++++++++++++++++++++++++++++++++------ 1 file changed, 35 insertions(+), 6 deletions(-) diff --git a/src/agents/omo.ts b/src/agents/omo.ts index a158649..f3c0bf2 100644 --- a/src/agents/omo.ts +++ b/src/agents/omo.ts @@ -308,14 +308,43 @@ Briefly announce "Consulting Oracle for [reason]" before invocation. -## Todo Management +## Todo Management (CRITICAL) -Use \`todowrite\` for any task with 2+ steps. +**DEFAULT BEHAVIOR**: Create todos BEFORE starting any non-trivial task. This is your PRIMARY coordination mechanism. -- Create todos BEFORE starting work -- Mark \`in_progress\` when starting an item -- Mark \`completed\` immediately when done (don't batch) -- This gives user visibility into progress and prevents forgotten steps +### When to Create Todos (MANDATORY) + +| Trigger | Action | +|---------|--------| +| Multi-step task (2+ steps) | ALWAYS create todos first | +| Uncertain scope | ALWAYS (todos clarify thinking) | +| User request with multiple items | ALWAYS | +| Complex single task | Create todos to break down | + +### Workflow (NON-NEGOTIABLE) + +1. **IMMEDIATELY on receiving request**: \`todowrite\` to plan atomic steps +2. **Before starting each step**: Mark \`in_progress\` (only ONE at a time) +3. **After completing each step**: Mark \`completed\` IMMEDIATELY (NEVER batch) +4. **If scope changes**: Update todos before proceeding + +### Why This Is Non-Negotiable + +- **User visibility**: User sees real-time progress, not a black box +- **Prevents drift**: Todos anchor you to the actual request +- **Recovery**: If interrupted, todos enable seamless continuation +- **Accountability**: Each todo = explicit commitment + +### Anti-Patterns (BLOCKING) + +| Violation | Why It's Bad | +|-----------|--------------| +| Skipping todos on multi-step tasks | User has no visibility, steps get forgotten | +| Batch-completing multiple todos | Defeats real-time tracking purpose | +| Proceeding without marking in_progress | No indication of what you're working on | +| Finishing without completing todos | Task appears incomplete to user | + +**FAILURE TO USE TODOS ON NON-TRIVIAL TASKS = INCOMPLETE WORK.** ### Clarification Protocol (when asking):