piercelamb/deep-implement

50 stars · Last commit 2026-02-28

Claude Code plugin that implements code from /deep-plan sections with TDD, code review, and git workflow

README preview

![deep-implement hero](assets/hero.jpeg)

# /deep-implement, a Claude Code plugin

![Version](https://img.shields.io/badge/version-0.2.1-blue)
![Status](https://img.shields.io/badge/status-beta-orange)
![License](https://img.shields.io/badge/license-MIT-green)
![Claude Code](https://img.shields.io/badge/Claude%20Code-Plugin-purple)
![Python](https://img.shields.io/badge/python-3.11%2B-blue)

> **Blog posts:**
> - [The Deep Trilogy](https://pierce-lamb.medium.com/the-deep-trilogy-claude-code-plugins-for-writing-good-software-fast-33b76f2a022d) - How the three plugins work together
> - [What I Learned](https://pierce-lamb.medium.com/what-i-learned-while-building-a-trilogy-of-claude-code-plugins-72121823172b) - Technical lessons from plugin development

`/deep-implement` is the final step in the deep planning pipeline. It takes the section files generated by [`/deep-plan`](https://github.com/piercelamb/deep-plan) and implements them one by one with TDD methodology, integrated code review, and a structured git workflow.

Where `/deep-plan` produces the *what* and *why*, `/deep-implement` handles the *how*—methodically, with tests first and human-in-the-loop code review at each step.

For large projects, use [`/deep-project`](https://github.com/piercelamb/deep-project) first to decompose vague requirements into focused specs, then `/deep-plan` each spec, then `/deep-implement` the resulting sections.

View full repository on GitHub →