ai-exchange/docs/automation_workflow_migration_checklist.md

Automation Workflow Migration Checklist

Use this checklist to move the proven autonomy-first Claude workflow from one computer to another and bootstrap a fresh project quickly.

1. Source files to copy

Copy these files from the source machine or source repository:

• docs/CLAUDE_template_autonomy_first.md
  • reusable base template for project CLAUDE.md
• docs/AI_协作自动化工作规程_v1.md
  • explanation of the working rules and why they were chosen
• docs/标准_CLAUDE_md_模板_v1.md
  • optional extra local reference if you want a second comparison template

If you already have a project-specific CLAUDE.md that worked well, copy that too.

2. Target placement on the new computer

Required placement

For each target project, place one active file at the project root:

• <project-root>/CLAUDE.md

Recommended source for that file:

• start from docs/CLAUDE_template_autonomy_first.md
• customize it for the new repository
• save the final version as <project-root>/CLAUDE.md

Optional reference placement

Keep the reusable references in a local docs area, for example:

• <project-root>/docs/CLAUDE_template_autonomy_first.md
• <project-root>/docs/AI_协作自动化工作规程_v1.md

This is useful when you want both:

• one active root CLAUDE.md
• one reusable reference copy for later edits

3. New machine prerequisite checklist

Before using the workflow on the target machine, confirm:

• Claude Code is installed and working
• the target repository can be opened locally
• the main language/runtime toolchain is installed
• the project package manager is installed
• the project test/typecheck/lint commands are known
• any required local services are available
• any needed credentials are already configured outside the repo

Examples of local services:

• database
• Redis
• Docker services
• cloud CLI auth

4. Initialize a new project with this workflow

Step 1. Create or copy the root file

• copy docs/CLAUDE_template_autonomy_first.md
• create <project-root>/CLAUDE.md
• paste the template into it

Step 2. Replace the placeholders

In the new root CLAUDE.md, fill in:

• project name
• one-paragraph project goal
• primary stack
• install command
• dev command
• test command
• typecheck command
• lint / format commands
• key architecture notes
• quality gates that must pass
• project-specific constraints

Step 3. Add project-local rules

Add any rules that are specific to the new repository, for example:

• strict typecheck must pass with zero errors
• database migrations must be additive only
• no mock database tests
• feature flags must gate new functionality
• do not change CI files without confirmation

Step 4. Keep the proven execution rules

Unless the new project truly needs different behavior, keep these intact:

• autonomy-first collaboration mode
• artifact over status
• small executable task breakdown
• continue after each completed task
• do not repeat the same blocker twice
• short factual milestone updates
• verify before reporting complete
• ask only for irreversible actions, missing resources, or product decisions

5. First-run project bootstrap checklist

After adding the new root CLAUDE.md, do this in the project:

• open the repository in Claude Code
• ask Claude to read the root CLAUDE.md
• ask Claude to inspect the repository structure
• ask Claude to identify the real quality gates
• ask Claude to create small executable tasks for the first milestone
• verify the first change is small and reversible
• confirm Claude reports artifacts, not just status

6. Quick validation checklist

Use this to confirm the workflow migrated correctly:

• Claude reads the root CLAUDE.md automatically
• Claude breaks non-trivial work into small tasks
• Claude edits files directly instead of lingering in planning
• Claude gives short milestone updates instead of repetitive status chatter
• Claude keeps moving without repeated confirmation on reversible steps
• Claude pauses only for real decision points or risky actions
• Claude verifies file existence or checks before claiming completion

7. Minimal file set for a lightweight migration

If you want the smallest useful transfer, only move these:

• docs/CLAUDE_template_autonomy_first.md
• create <project-root>/CLAUDE.md from it

That is enough to reproduce the main behavior.

8. Recommended file set for a full migration

For a more complete transfer, move these:

• docs/CLAUDE_template_autonomy_first.md
• docs/AI_协作自动化工作规程_v1.md
• current project’s final CLAUDE.md if it has proven repo-specific rules

This gives you:

• the reusable template
• the rationale document
• one real working example

9. Common migration mistakes

Avoid these mistakes:

• copying only the idea, but not the actual CLAUDE.md file
• placing the template in docs/ but forgetting to create root CLAUDE.md
• leaving placeholder commands unfilled
• keeping broad vague tasks instead of small executable tasks
• accepting status reports without artifact checks
• letting the workflow stop after each small reversible step
• forgetting to document real project quality gates

10. Recommended startup prompt for a new repo

After placing the new root CLAUDE.md, a good initialization prompt is:

Read the root CLAUDE.md, inspect this repository, identify the real quality gates, then create a small autonomy-first task breakdown for the first milestone and start executing the first concrete reversible step.

11. Completion criteria

The migration is complete when:

• the new machine has Claude Code working
• the target project has a root CLAUDE.md
• the root file contains real project commands and constraints
• Claude follows artifact-driven execution in practice
• the first milestone is decomposed into small tasks
• the first real change is written and verified successfully