Migration Diary: Freeze a Golden Task Fixture Before You Leave a Paid Coding Agent

Описание и применение

Создайте небольшую, управляемую схему «золотых» задач, чтобы зафиксировать требования, которые ранее определялись чат‑транскриптами AI‑агента, и используйте её для проверки качества после перехода на новый стек.

Задача

When a paid coding agent subscription ends, the team loses the chat‑based acceptance surface that defined what "done" looked like, risking quality drift on the new stack.

Результат

The team now has a lightweight, versioned test suite that captures the agent’s implicit acceptance criteria, allowing them to safely cancel the paid subscription without risking quality regression.

Рабочий процесс

• 1. Identify recent agent‑drafted changes from merge history and write concise task descriptions.
• 2. Freeze pre‑change files as inputs next to each task prompt.
• 3. Create a runner that applies the frozen inputs, invokes the new local agent command, and asserts file changes and test results.
• 4. Execute the runner to ensure tasks pass; failures indicate destination drift.
• 5. Commit the fixture suite and runner to the repository for ongoing regression testing.

Доказательства

A frozen fixture turns those unspoken expectations into files you can rerun on cheaper local or remote infrastructure.

Источник

The paid agent also absorbed style rules, review nits, and file‑ban instincts that never landed in git.

Источник