What "Done" Actually Means: A Day Inside the Ticket-to-Ship Loop

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

Автоматизированный цикл от тикета до поставки, использующий Claude Code skill, устраняет недопонимания между продуктом и разработчиком, обеспечивая план, проверки и обязательные тесты, что снижает количество исправлений и повышает согласованность "готово".

Задача

Misalignment between product intent and developer implementation causes scope drift, rework, and costly fixes.

Результат

Implemented a disciplined, AI‑assisted workflow that reduces misunderstandings, eliminates unnecessary rework, and ensures all stakeholders share a common definition of "done."

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

• Pull ticket and read CLAUDE.md
• Generate requirement plan and ask for user approval
• Build backend fields, DTOs, services, controller, migration
• Ask for review after each logical unit
• Run all tests (dotnet build/test, ng build/test)
• Perform code review on local diff before MR
• Translate changes into a product‑friendly handover
• Handle QA findings in a single loop

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

The skill pulls the ticket, reads the project's CLAUDE.md, checks memory for anything related from a prior sprint. Then it asks something most AI coding tools skip straight past: what does this actually require, before writing a line of code?

Источник

Phase 5 runs engineering:code-review against the local diff, before any MR exists.

Источник