defract + Claude Code: take one feature through a reviewable process

Make the feature small enough to review

Thanks to defract for sponsoring this video.

Luke’s test is a visual pipeline view for an existing SaaS, starting from a one-line request. The repository and its current behaviour provide the context.

1. Set up defract against the intended repository.
2. Review open questions and scope before accepting the feature plan.
3. Write acceptance criteria describing visible behaviour and how you will know it works.

Approve the interface and architecture

The walkthrough shows mockups, architecture decisions and a diagram before code is written.

1. Inspect the design against the real task, including empty states and the existing app.
2. Review the architecture diagram and list of files the change will touch.
3. Resolve ambiguous permissions, data handling and behaviour in the plan instead of letting implementation invent them.

Implement, test and release to staging

The video hands manual tests to Codex, feeds fixes back as a change request, then reviews the report and release notes.

1. Run the implementation and inspect the change against the acceptance criteria.
2. Complete the manual test sequence and record a concrete reproduction for any failure.
3. Review the fixes, release notes and staging result before considering production.

The takeaway

The value is an inspectable development process. A completed implementation is still followed by review and staging checks.