Rename product from agent-framework to automaton; move scripts to scripts/ folder
This commit is contained in:
@@ -98,7 +98,7 @@ Do not begin any research, implementation, or bug-finding tasks.
|
||||
|
||||
## Project Upgrade
|
||||
|
||||
When a user asks to "upgrade the agent-framework for this project," the agent should:
|
||||
When a user asks to "upgrade automaton for this project," the agent should:
|
||||
|
||||
### Upgrade Process
|
||||
|
||||
@@ -129,25 +129,25 @@ The agent should report:
|
||||
### Example Upgrade Scenarios
|
||||
|
||||
**Scenario 1: New file added globally**
|
||||
- User says: "Upgrade the agent-framework for this project"
|
||||
- User says: "Upgrade automaton for this project"
|
||||
- Agent detects that `prompts/test_design.md` is missing from the project's framework
|
||||
- Agent copies `prompts/test_design.md` from the global framework into the project's framework
|
||||
- Agent reports: "Upgraded: Added prompts/test_design.md. Your framework is now up to date."
|
||||
|
||||
**Scenario 2: Global file changed, project hasn't customized it**
|
||||
- User says: "Upgrade the agent-framework for this project"
|
||||
- User says: "Upgrade automaton for this project"
|
||||
- Agent detects that `prompts/orchestrate.md` has changed in the global framework, and the project's version is identical to the old global version
|
||||
- Agent copies `prompts/orchestrate.md` from the global framework into the project's framework
|
||||
- Agent reports: "Upgraded: Updated prompts/orchestrate.md. Your framework is now up to date."
|
||||
|
||||
**Scenario 3: Global file changed, project has customized it**
|
||||
- User says: "Upgrade the agent-framework for this project"
|
||||
- User says: "Upgrade automaton for this project"
|
||||
- Agent detects that `prompts/orchestrate.md` has changed in the global framework, and the project's version differs from the global version
|
||||
- Agent keeps the project's version of `prompts/orchestrate.md`
|
||||
- Agent reports: "Skipped: prompts/orchestrate.md (customized in your project). Your framework is now up to date."
|
||||
|
||||
**Scenario 4: Multiple changes**
|
||||
- User says: "Upgrade the agent-framework for this project"
|
||||
- User says: "Upgrade automaton for this project"
|
||||
- Agent detects:
|
||||
- `prompts/test_design.md` is new → **Added**
|
||||
- `prompts/workflow.md` has changed, project hasn't customized → **Upgraded**
|
||||
|
||||
+1
-1
@@ -1,6 +1,6 @@
|
||||
# Workflow State Machine
|
||||
|
||||
This file defines the linear progression of a task in the agent-framework. The Orchestrator uses this to determine the next phase.
|
||||
This file defines the linear progression of a task in automaton. The Orchestrator uses this to determine the next phase.
|
||||
|
||||
## Task Lifecycle
|
||||
|
||||
|
||||
Reference in New Issue
Block a user