From 03d9ed5a9c30089659a3d4ea76792c86267eee01 Mon Sep 17 00:00:00 2001 From: laptran Date: Sat, 13 Jun 2026 21:41:42 -0400 Subject: [PATCH] Update 'upgrade automaton for this project' flow to handle task migration The onboarding Migration Check now also detects tasks at the deprecated {project}/tasks/ location and moves them to .automaton/tasks/. --- prompts/onboarding.md | 8 ++++++-- 1 file changed, 6 insertions(+), 2 deletions(-) diff --git a/prompts/onboarding.md b/prompts/onboarding.md index 51fa23d..bb0cc73 100644 --- a/prompts/onboarding.md +++ b/prompts/onboarding.md @@ -88,7 +88,7 @@ Do not begin any research, implementation, or bug-finding tasks. ## Migration Check -When a user asks to "upgrade automaton for this project" or during onboarding, the agent should first check if the project has stale copies of framework files (from the old model where files were copied into the project): +When a user asks to "upgrade automaton for this project" or during onboarding, the agent should first check if the project has stale copies of framework files (from the old model where files were copied into the project) or tasks in the deprecated location. ### Migration Detection @@ -98,12 +98,16 @@ When a user asks to "upgrade automaton for this project" or during onboarding, t - `scripts/` directory with files matching global scripts - Any other files that exist in `~/.automaton/` -2. If stale files are found, offer to run migration: +2. Check for tasks at the deprecated `{project}/tasks/` location: + - If `{project}/tasks/` exists but `{project}/.automaton/tasks/` does not, tasks need to be moved. + +3. If stale files or deprecated task location are found, offer to run migration: - Run `~/.automaton/scripts/migrate-project.sh {project}` if available - Or manually: - Files identical to global → delete (framework provides them) - Files different from global → move to `.automaton/extensions/` - `.agent.md` and `.rules.md` → keep as-is + - `{project}/tasks/` → move to `{project}/.automaton/tasks/` ### After Migration