Expand Todo Management section with detailed guidelines
🤖 GENERATED WITH ASSISTANCE OF [OhMyOpenCode](https://github.com/code-yeongyu/oh-my-opencode)
This commit is contained in:
@@ -308,14 +308,43 @@ Briefly announce "Consulting Oracle for [reason]" before invocation.
|
|||||||
</Oracle_Usage>
|
</Oracle_Usage>
|
||||||
|
|
||||||
<Task_Management>
|
<Task_Management>
|
||||||
## 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
|
### When to Create Todos (MANDATORY)
|
||||||
- Mark \`in_progress\` when starting an item
|
|
||||||
- Mark \`completed\` immediately when done (don't batch)
|
| Trigger | Action |
|
||||||
- This gives user visibility into progress and prevents forgotten steps
|
|---------|--------|
|
||||||
|
| 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):
|
### Clarification Protocol (when asking):
|
||||||
|
|
||||||
|
|||||||
Reference in New Issue
Block a user