You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
PR #556 (merged 2026-03-06) made substantive prompt changes to kelos-fake-strategist.yaml β removing the "Workflow Improvements" focus area, widening the dedup search window, and adding cross-agent boundaries. These changes were not propagated to self-development/tasks/fake-strategist-task.yaml, creating significant prompt drift that affects manual strategist runs via the run-fake-strategist.yaml workflow.
The open PR #551 (which addresses issue #544 about task template drift) only covers cosmetic changes identified before#556 merged β it does not include these newer, more impactful divergences.
Findings
1. "Workflow Improvements" focus area still present in task template (removed from TaskSpawner)
PR #556 deliberately removed focus area #2 ("Workflow Improvements") from kelos-fake-strategist.yaml to reduce inter-agent overlap β this area is handled by kelos-self-update and kelos-config-update. The TaskSpawner now has 3 focus areas.
Task template (tasks/fake-strategist-task.yaml, lines 34-58) β still has 4 focus areas:
New Use Cases
Workflow Improvements β removed from TaskSpawner
Integration Opportunities
New CRDs & API Extensions
Impact: Manual strategist runs via run-fake-strategist.yaml may choose "Workflow Improvements" as their focus area, producing issues that overlap with kelos-self-update and kelos-config-update output β exactly the problem #556 was designed to prevent.
2. Dedup search window not widened in task template
PR #556 changed the dedup search from --limit 10 to --limit 50 --json number,title across all cron agents.
TaskSpawner (kelos-fake-strategist.yaml, line 70):
gh issue list --label generated-by-kelos --state open --limit 50 --json number,title
Task template (tasks/fake-strategist-task.yaml, line 71):
gh issue list --label generated-by-kelos --limit 10
Impact: Manual strategist runs only check the 10 most recent issues for duplicates, missing 40+ existing issues. With 40+ open generated-by-kelos issues, this makes duplicate creation likely.
3. Cross-agent awareness constraints missing from task template
PR #556 added explicit cross-agent boundaries to the TaskSpawner (lines 71-74):
- The following areas are handled by other agents β do not create issues about them:
- Self-development workflow improvements, prompt tuning, config alignment β kelos-self-update
- Documentation, CLI UX, error messages β kelos-fake-user
- Agent configuration based on PR reviews β kelos-config-update
The task template has none of these constraints (lines 66-72). Manual runs lack any awareness of other agents' responsibilities.
4. "Exit without output" constraint missing from task template
The TaskSpawner includes (line 75):
- If after reviewing existing issues you cannot identify something genuinely new and actionable, exit without creating an issue or PR. Not every run needs to produce output
The task template only says (line 72):
- If after reviewing existing issues you cannot identify something genuinely new and actionable, exit without creating an issue or PR. Not every run needs to produce output
Wait β actually the task template does have a similar line. Let me check... The task template's version (line 72) is weaker:
- If after reviewing existing issues you cannot identify something genuinely new and actionable, exit without creating an issue or PR. Not every run needs to produce output
This line was present before #556 but is equivalent. No gap here β correction: this finding is not applicable.
Proposed Changes
Sync fake-strategist-task.yaml prompt with kelos-fake-strategist.yaml
Replace the task template's prompt section (lines 29-72) with the current TaskSpawner prompt content. Specifically:
Since PR #551 is still open and addresses #544, the simplest approach is to update #551 to include these additional sync changes. Alternatively, a new PR can address the #556-related drift separately.
π€ Kelos Agent @gjkim42
Area: Task Template Maintenance
Summary
PR #556 (merged 2026-03-06) made substantive prompt changes to
kelos-fake-strategist.yamlβ removing the "Workflow Improvements" focus area, widening the dedup search window, and adding cross-agent boundaries. These changes were not propagated toself-development/tasks/fake-strategist-task.yaml, creating significant prompt drift that affects manual strategist runs via therun-fake-strategist.yamlworkflow.The open PR #551 (which addresses issue #544 about task template drift) only covers cosmetic changes identified before #556 merged β it does not include these newer, more impactful divergences.
Findings
1. "Workflow Improvements" focus area still present in task template (removed from TaskSpawner)
PR #556 deliberately removed focus area #2 ("Workflow Improvements") from
kelos-fake-strategist.yamlto reduce inter-agent overlap β this area is handled bykelos-self-updateandkelos-config-update. The TaskSpawner now has 3 focus areas.TaskSpawner (
kelos-fake-strategist.yaml, lines 39-55) β 3 focus areas:Task template (
tasks/fake-strategist-task.yaml, lines 34-58) β still has 4 focus areas:Impact: Manual strategist runs via
run-fake-strategist.yamlmay choose "Workflow Improvements" as their focus area, producing issues that overlap withkelos-self-updateandkelos-config-updateoutput β exactly the problem #556 was designed to prevent.2. Dedup search window not widened in task template
PR #556 changed the dedup search from
--limit 10to--limit 50 --json number,titleacross all cron agents.TaskSpawner (
kelos-fake-strategist.yaml, line 70):Task template (
tasks/fake-strategist-task.yaml, line 71):Impact: Manual strategist runs only check the 10 most recent issues for duplicates, missing 40+ existing issues. With 40+ open
generated-by-kelosissues, this makes duplicate creation likely.3. Cross-agent awareness constraints missing from task template
PR #556 added explicit cross-agent boundaries to the TaskSpawner (lines 71-74):
The task template has none of these constraints (lines 66-72). Manual runs lack any awareness of other agents' responsibilities.
4. "Exit without output" constraint missing from task template
The TaskSpawner includes (line 75):
The task template only says (line 72):
Wait β actually the task template does have a similar line. Let me check... The task template's version (line 72) is weaker:
This line was present before #556 but is equivalent. No gap here β correction: this finding is not applicable.
Proposed Changes
Sync
fake-strategist-task.yamlprompt withkelos-fake-strategist.yamlReplace the task template's prompt section (lines 29-72) with the current TaskSpawner prompt content. Specifically:
--limit 10with--state open --limit 50 --json number,title(line 71)gh issue createcommand (PR Sync task templates with TaskSpawners and document tasks/ directoryΒ #551 already proposes this)Update PR #551 or create a new PR
Since PR #551 is still open and addresses #544, the simplest approach is to update #551 to include these additional sync changes. Alternatively, a new PR can address the #556-related drift separately.
Relationship to existing issues
This issue specifically tracks the new drift introduced by #556 that is not covered by the existing #544/#551 pair.
Evidence
kelos-fake-strategist.yaml, widened dedup to--limit 50, added cross-agent constraintstasks/fake-strategist-task.yamlon main: still contains all 4 focus areas,--limit 10, no cross-agent constraintsrun-fake-strategist.yamlworkflow: directly appliestasks/fake-strategist-task.yaml, meaning manual runs use the outdated prompt/kind cleanup