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

Use scope, design and architecture to resolve decisions before implementation.

[HTML](https://lukejbyrne.com/library/guides/h7h0c_u-lyg/)
Content language: en
Author: Luke Byrne
Video published: 2026-09-13
Guide published: 2026-10-31
Sponsored coverage: defract

[Watch the video](https://www.youtube.com/watch?v=H7h0C_u-Lyg)
Video language: English

## 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.

## Workflow resources

- [defract.dev](https://defract.dev/luke)

## Chapters

- [0:00 Giving Claude Code a full dev team](https://www.youtube.com/watch?v=H7h0C_u-Lyg&t=0s)
- [1:34 The test: a pipeline view for my real SaaS](https://www.youtube.com/watch?v=H7h0C_u-Lyg&t=94s)
- [2:08 Setting up defract on a real repo](https://www.youtube.com/watch?v=H7h0C_u-Lyg&t=128s)
- [4:18 Scope: open questions and acceptance criteria](https://www.youtube.com/watch?v=H7h0C_u-Lyg&t=258s)
- [8:13 Design: mockups before any code](https://www.youtube.com/watch?v=H7h0C_u-Lyg&t=493s)
- [9:22 Architecture decisions and diagram](https://www.youtube.com/watch?v=H7h0C_u-Lyg&t=562s)
- [11:39 Implementation and manual tests](https://www.youtube.com/watch?v=H7h0C_u-Lyg&t=699s)
- [14:27 Review, release and shipping to staging](https://www.youtube.com/watch?v=H7h0C_u-Lyg&t=867s)

## Sources and limitations

Written follow-along guide prepared 31 October 2026 from this exact published video’s description and chapter sequence. The checklists are editorial adaptations, not verbatim transcript quotations. Demonstrated results are attributed to the video; the full final video was not independently transcribed or watched for this article, and the product was not retested. For installation commands, later interface changes and current offers, use the original resources linked here.

[Original video](https://www.youtube.com/watch?v=H7h0C_u-Lyg)