hermes/agent-framework
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Fix bugs 1-11: interactive research/design, doc review phase, orchestrator state machine, design phase in workflow, fix verdict task creation contradiction

Browse Source
This commit is contained in:
gitea
2026-06-10 23:44:55 -04:00
parent 3cdb95e083
commit 3ac1b0858b
12 changed files with 600 additions and 553 deletions
Download Patch File Download Diff File Expand all files Collapse all files
README.md
+23 -8
View File
@@ -49,21 +49,36 @@ If you prefer to set it up manually, create a `.agent-framework/` directory in y
The framework features an **Autopilot** mode that allows the agent to drive a project to completion with minimal intervention.
### Lifecycle of a Task
1. **Research**: Produce a `SPEC.md` (Contract). No code allowed.
2. **Implement**: Write code and tests based *only* on the `SPEC.md`.
3. **Bug Find**: Aggressive search for bugs and spec deviations.
4. **Adversarial Bug Find**: Deep search for complex logic errors, race conditions, and performance issues.
5. **Referee**: Objective evaluation of all bugs and the final verdict.
1. **Research**: Produce a `SPEC.md` (Contract). No code allowed. **Interactive** — agent grills you for requirements and gets sign-off.
2. **Design** (optional): Produce a `DESIGN.md` (Architecture). No code allowed. **Interactive** — agent grills you for design decisions and gets sign-off.
3. **Implement**: Write code and tests based *only* on the `SPEC.md` (and `DESIGN.md` if present).
4. **Bug Find**: Aggressive search for bugs and spec deviations.
5. **Adversarial Bug Find**: Deep search for complex logic errors, race conditions, and performance issues.
6. **Doc Review**: Review documentation against DESIGN.md plan and fix missing docs.
7. **Referee**: Objective evaluation of all bugs, docs, and the final verdict.
### How to use Autopilot
Add `Autopilot: Enabled` to your project's `.agent-framework/AGENT.md` and use the following command:
> *"Initialize Autopilot for this project. Scan the tasks/ directory and report the current status of all tasks and the recommended next actions."*
#### Autopilot mode
Add `Autopilot: Enabled` to your project's `.agent-framework/AGENT.md` and just say:
- **Start a new task**: "Research add user authentication" (the Orchestrator creates the task and drives it all the way to completion)
- **Continue**: "orchestrate" or "continue" (the Orchestrator finds the most advanced task and drives it)
#### Manual mode
Set `Autopilot: Disabled` (or leave it unset) in `AGENT.md`. The Orchestrator reports the current state and tells you the next command. Then run phases by saying things like:
- "Research add user authentication" — starts a new task
- "Design the add-user-auth task" — designs the architecture (optional)
- "Implement the add-user-auth task" — implements the task
- "Find bugs in the add-user-auth task" — finds bugs
- "Perform adversarial bug find for add-user-auth" — deep bug search
- "Review docs for the add-user-auth task" — reviews documentation
- "Review the add-user-auth task" — referee evaluates
- "orchestrate" — asks the Orchestrator what to do next
## Key Components
- `AGENT.md`: Project-specific configuration and mode selection.
- `RULES.md`: Living document of project constraints and past failure modes.
- `prompts/`: Specialized system prompts for each phase (Research, Implement, Bug Finder, etc.).
- `prompts/`: Specialized system prompts for each phase (Research, Design, Implement, Bug Finder, Adversarial Bug Finder, Doc Review, Referee, etc.).
- `workflow.md`: The state machine governing the Autopilot lifecycle.
## Contact & Support