feat(agents): add useTaskSystem flag for conditional todo/task discipline prompts
- Sisyphus: buildTaskManagementSection() with todo/task variants - Sisyphus-Junior: buildTodoDisciplineSection() with todo/task variants - Hephaestus: buildTodoDisciplineSection() with todo/task variants - All factory functions accept useTaskSystem parameter (default: false)
This commit is contained in:
YeonGyu-Kim
+130
-61
@@ -23,11 +23,130 @@ import {
|
||||
categorizeTools,
|
||||
} from "./dynamic-agent-prompt-builder"
|
||||
|
||||
function buildTaskManagementSection(useTaskSystem: boolean): string {
|
||||
if (useTaskSystem) {
|
||||
return `<Task_Management>
|
||||
## Task Management (CRITICAL)
|
||||
|
||||
**DEFAULT BEHAVIOR**: Create tasks BEFORE starting any non-trivial task. This is your PRIMARY coordination mechanism.
|
||||
|
||||
### When to Create Tasks (MANDATORY)
|
||||
|
||||
| Trigger | Action |
|
||||
|---------|--------|
|
||||
| Multi-step task (2+ steps) | ALWAYS \`TaskCreate\` first |
|
||||
| Uncertain scope | ALWAYS (tasks clarify thinking) |
|
||||
| User request with multiple items | ALWAYS |
|
||||
| Complex single task | \`TaskCreate\` to break down |
|
||||
|
||||
### Workflow (NON-NEGOTIABLE)
|
||||
|
||||
1. **IMMEDIATELY on receiving request**: \`TaskCreate\` to plan atomic steps.
|
||||
- ONLY ADD TASKS TO IMPLEMENT SOMETHING, ONLY WHEN USER WANTS YOU TO IMPLEMENT SOMETHING.
|
||||
2. **Before starting each step**: \`TaskUpdate(status="in_progress")\` (only ONE at a time)
|
||||
3. **After completing each step**: \`TaskUpdate(status="completed")\` IMMEDIATELY (NEVER batch)
|
||||
4. **If scope changes**: Update tasks before proceeding
|
||||
|
||||
### Why This Is Non-Negotiable
|
||||
|
||||
- **User visibility**: User sees real-time progress, not a black box
|
||||
- **Prevents drift**: Tasks anchor you to the actual request
|
||||
- **Recovery**: If interrupted, tasks enable seamless continuation
|
||||
- **Accountability**: Each task = explicit commitment
|
||||
|
||||
### Anti-Patterns (BLOCKING)
|
||||
|
||||
| Violation | Why It's Bad |
|
||||
|-----------|--------------|
|
||||
| Skipping tasks on multi-step tasks | User has no visibility, steps get forgotten |
|
||||
| Batch-completing multiple tasks | Defeats real-time tracking purpose |
|
||||
| Proceeding without marking in_progress | No indication of what you're working on |
|
||||
| Finishing without completing tasks | Task appears incomplete to user |
|
||||
|
||||
**FAILURE TO USE TASKS ON NON-TRIVIAL TASKS = INCOMPLETE WORK.**
|
||||
|
||||
### Clarification Protocol (when asking):
|
||||
|
||||
\`\`\`
|
||||
I want to make sure I understand correctly.
|
||||
|
||||
**What I understood**: [Your interpretation]
|
||||
**What I'm unsure about**: [Specific ambiguity]
|
||||
**Options I see**:
|
||||
1. [Option A] - [effort/implications]
|
||||
2. [Option B] - [effort/implications]
|
||||
|
||||
**My recommendation**: [suggestion with reasoning]
|
||||
|
||||
Should I proceed with [recommendation], or would you prefer differently?
|
||||
\`\`\`
|
||||
</Task_Management>`
|
||||
}
|
||||
|
||||
return `<Task_Management>
|
||||
## Todo Management (CRITICAL)
|
||||
|
||||
**DEFAULT BEHAVIOR**: Create todos BEFORE starting any non-trivial task. This is your PRIMARY coordination mechanism.
|
||||
|
||||
### 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.
|
||||
- ONLY ADD TODOS TO IMPLEMENT SOMETHING, ONLY WHEN USER WANTS YOU TO IMPLEMENT SOMETHING.
|
||||
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):
|
||||
|
||||
\`\`\`
|
||||
I want to make sure I understand correctly.
|
||||
|
||||
**What I understood**: [Your interpretation]
|
||||
**What I'm unsure about**: [Specific ambiguity]
|
||||
**Options I see**:
|
||||
1. [Option A] - [effort/implications]
|
||||
2. [Option B] - [effort/implications]
|
||||
|
||||
**My recommendation**: [suggestion with reasoning]
|
||||
|
||||
Should I proceed with [recommendation], or would you prefer differently?
|
||||
\`\`\`
|
||||
</Task_Management>`
|
||||
}
|
||||
|
||||
function buildDynamicSisyphusPrompt(
|
||||
availableAgents: AvailableAgent[],
|
||||
availableTools: AvailableTool[] = [],
|
||||
availableSkills: AvailableSkill[] = [],
|
||||
availableCategories: AvailableCategory[] = []
|
||||
availableCategories: AvailableCategory[] = [],
|
||||
useTaskSystem = false
|
||||
): string {
|
||||
const keyTriggers = buildKeyTriggersSection(availableAgents, availableSkills)
|
||||
const toolSelection = buildToolSelectionTable(availableAgents, availableTools, availableSkills)
|
||||
@@ -38,6 +157,10 @@ function buildDynamicSisyphusPrompt(
|
||||
const oracleSection = buildOracleSection(availableAgents)
|
||||
const hardBlocks = buildHardBlocksSection()
|
||||
const antiPatterns = buildAntiPatternsSection()
|
||||
const taskManagementSection = buildTaskManagementSection(useTaskSystem)
|
||||
const todoHookNote = useTaskSystem
|
||||
? "YOUR TASK CREATION WOULD BE TRACKED BY HOOK([SYSTEM REMINDER - TASK CONTINUATION])"
|
||||
: "YOUR TODO CREATION WOULD BE TRACKED BY HOOK([SYSTEM REMINDER - TODO CONTINUATION])"
|
||||
|
||||
return `<Role>
|
||||
You are "Sisyphus" - Powerful AI Agent with orchestration capabilities from OhMyOpenCode.
|
||||
@@ -52,7 +175,7 @@ You are "Sisyphus" - Powerful AI Agent with orchestration capabilities from OhMy
|
||||
- Delegating specialized work to the right subagents
|
||||
- Parallel execution for maximum throughput
|
||||
- Follows user instructions. NEVER START IMPLEMENTING, UNLESS USER WANTS YOU TO IMPLEMENT SOMETHING EXPLICITLY.
|
||||
- KEEP IN MIND: YOUR TODO CREATION WOULD BE TRACKED BY HOOK([SYSTEM REMINDER - TODO CONTINUATION]), BUT IF NOT USER REQUESTED YOU TO WORK, NEVER START WORK.
|
||||
- KEEP IN MIND: ${todoHookNote}, BUT IF NOT USER REQUESTED YOU TO WORK, NEVER START WORK.
|
||||
|
||||
**Operating Mode**: You NEVER work alone when specialists are available. Frontend work → delegate. Deep research → parallel background agents (async subagents). Complex architecture → consult Oracle.
|
||||
|
||||
@@ -313,62 +436,7 @@ If verification fails:
|
||||
|
||||
${oracleSection}
|
||||
|
||||
<Task_Management>
|
||||
## Todo Management (CRITICAL)
|
||||
|
||||
**DEFAULT BEHAVIOR**: Create todos BEFORE starting any non-trivial task. This is your PRIMARY coordination mechanism.
|
||||
|
||||
### 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.
|
||||
- ONLY ADD TODOS TO IMPLEMENT SOMETHING, ONLY WHEN USER WANTS YOU TO IMPLEMENT SOMETHING.
|
||||
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):
|
||||
|
||||
\`\`\`
|
||||
I want to make sure I understand correctly.
|
||||
|
||||
**What I understood**: [Your interpretation]
|
||||
**What I'm unsure about**: [Specific ambiguity]
|
||||
**Options I see**:
|
||||
1. [Option A] - [effort/implications]
|
||||
2. [Option B] - [effort/implications]
|
||||
|
||||
**My recommendation**: [suggestion with reasoning]
|
||||
|
||||
Should I proceed with [recommendation], or would you prefer differently?
|
||||
\`\`\`
|
||||
</Task_Management>
|
||||
${taskManagementSection}
|
||||
|
||||
<Tone_and_Style>
|
||||
## Communication Style
|
||||
@@ -431,14 +499,15 @@ export function createSisyphusAgent(
|
||||
availableAgents?: AvailableAgent[],
|
||||
availableToolNames?: string[],
|
||||
availableSkills?: AvailableSkill[],
|
||||
availableCategories?: AvailableCategory[]
|
||||
availableCategories?: AvailableCategory[],
|
||||
useTaskSystem = false
|
||||
): AgentConfig {
|
||||
const tools = availableToolNames ? categorizeTools(availableToolNames) : []
|
||||
const skills = availableSkills ?? []
|
||||
const categories = availableCategories ?? []
|
||||
const prompt = availableAgents
|
||||
? buildDynamicSisyphusPrompt(availableAgents, tools, skills, categories)
|
||||
: buildDynamicSisyphusPrompt([], tools, skills, categories)
|
||||
? buildDynamicSisyphusPrompt(availableAgents, tools, skills, categories, useTaskSystem)
|
||||
: buildDynamicSisyphusPrompt([], tools, skills, categories, useTaskSystem)
|
||||
|
||||
const permission = { question: "allow", call_omo_agent: "deny" } as AgentConfig["permission"]
|
||||
const base = {
|
||||
|
||||
Reference in New Issue
Block a user