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

Description and use

An AI‑assisted ticket‑to‑ship cycle that clarifies requirements, enforces planning, checkpoints, mandatory tests, pre‑merge review, and a product‑friendly handover, reducing rework and aligning the definition of "done."

Problem

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

Outcome

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

Workflow

• 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

Evidence

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?

Source

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

Source