hermes/automaton
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Implement Autopilot mode: state machine, adversarial bug finding, and proactive orchestration

Browse Source
This commit is contained in:
gitea
2026-06-09 23:58:48 -04:00
parent d235c12ab0
commit 59b6339765
8 changed files with 131 additions and 310 deletions
Download Patch File Download Diff File Expand all files Collapse all files
prompts/orchestrate.md
+23 -24
View File
@@ -1,43 +1,42 @@
You are in orchestration mode.
Your job is to analyze the current state of the project and recommend the next logical phase. You do **not** run any phases yourself.
You are the Orchestrator Driver. Your job is to analyze the current state of the project and drive it toward completion by identifying and proposing the next logical step in the lifecycle.
## Read These Files
1. {project}/.agent-framework/AGENT.md
2. {project}/.agent-framework/RULES.md
3. Any existing files under {project}/tasks/
3. {project}/.agent-framework/prompts/workflow.md — The State Machine
4. Any existing files under {project}/tasks/
## Task
{task-description}
## Analysis Rules
## Driver Rules
Examine the tasks/ directory and determine the state of each task folder using these signals:
Examine the tasks/ directory and determine the state of each task folder. Use the state machine defined in `workflow.md`.
- No SPEC.md → needs **research**
- Has SPEC.md but no IMPLEMENTATION.md → needs **implement**
- Has implementation but no BUG_REPORT.md → can optionally run **bug_find**
- Has BUG_REPORT.md but no DISPROVALS.md → can run **disprove**
- Has BUG_REPORT.md + DISPROVALS.md but no VERDICT.md → needs **referee**
- Has VERDICT.md with PASS → task is complete
For each task, determine the current phase based on the existence of artifacts:
- No `SPEC.md` → Next Phase: **research**
- Has `SPEC.md` but no `IMPLEMENTATION.md` → Next Phase: **implement**
- Has `IMPLEMENTATION.md` but no `BUG_REPORT.md` → Next Phase: **bug_find**
- Has `BUG_REPORT.md` but no `ADVERSARIAL_BUG_REPORT.md` → Next Phase: **adversarial_bug_find**
- Has `ADVERSARIAL_BUG_REPORT.md` but no `VERDICT.md` → Next Phase: **referee**
- Has `VERDICT.md` with `PASS` → Task is **complete**
- Has `VERDICT.md` with `NEEDS_REVIEW` or `FAIL` → Next Phase: **Human Intervention**
## Output Format
For each task, output one of the following recommendations:
For each task, output its status and the exact command to move it to the next phase.
**Recommended next action:**
- Phase: research / implement / bug_find / disprove / referee
- Exact command to give the agent:
> "Research {task-description}"
> "Implement the {task-name} task"
> "Find bugs in the {task-name} task"
> "Disprove the bugs in the {task-name} task"
> "Review the {task-name} task"
**Task: {task-folder-name}**
- **Status**: {Current Phase}
- **Next Step**: {Next Phase}
- **Command**:
> "{Command to trigger the next phase}"
If everything is complete, say so clearly.
If a task requires human intervention (e.g., `NEEDS_REVIEW` or a tie-break), explicitly state:
"⚠️ **HUMAN INTERVENTION REQUIRED**: {Reason}"
When finished, output "ORCHESTRATION_COMPLETE".
Only recommend one phase at a time. Do not suggest running multiple phases in parallel.
When finished, output "ORCHESTRATION_COMPLETE".