Code Migration Checkpoints

复制 Prompt

/goal
GOAL:
Complete Code Migration Checkpoints for a migration project: Inventory legacy assumptions, map them to a target stack, and execute the migration through validated checkpoints.

CONTEXT:
- Before editing, read the nearest AGENTS.md/CLAUDE.md, current issue or PLAN.md, and any failing logs already in the repo.
- Inspect legacy code, target implementation, compatibility tests, visual snapshots, and migration notes.
- Establish a baseline by running or locating evidence for: `legacy assumption inventory, checkpoint migration plan, lint, type-check, focused tests after each milestone, rollback notes`.

CONSTRAINTS:
- Keep the scope limited to this goal; do not expand into unrelated cleanup.
- Do not weaken tests, delete assertions, or mask errors to make verification pass.
- Respect the repository's AGENTS.md/CLAUDE.md instructions and existing patterns.
- Preserve existing user-visible behavior unless the goal explicitly names a behavior change.
- Keep compatibility evidence for the old and new paths until the migration is verified.

DONE WHEN:
- The implementation or documentation directly satisfies: Inventory legacy assumptions, map them to a target stack, and execute the migration through validated checkpoints.
- The verification command or evidence path succeeds: `legacy assumption inventory, checkpoint migration plan, lint, type-check, focused tests after each milestone, rollback notes`.
- The final diff is scoped to the relevant files and has no unrelated formatting churn.

VERIFY:
- Run `legacy assumption inventory, checkpoint migration plan, lint, type-check, focused tests after each milestone, rollback notes` or the closest repo-local equivalent if the exact command is not available.
- Capture before/after evidence for the behavior, metric, report, or artifact involved.
- If verification cannot run locally, stop and report the missing dependency instead of guessing success.

OUTPUT:
- Summarize changed files, key decisions, verification output, and remaining risks.
- Include any follow-up that is required for production rollout or human review.

STOP RULES:
- Pause if secrets, production access, stakeholder decisions, or destructive data operations are required.
- Pause after three failed fix attempts on the same symptom and challenge the root-cause hypothesis.
- Do not mark the goal complete until the current repository state has been audited against DONE WHEN.