Deep Implement

/deep-implement, a Claude Code plugin
Blog posts:
- The Deep Trilogy - How the three plugins work together
- What I Learned - 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 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 first to decompose vague requirements into focused specs, then /deep-plan each spec, then /deep-implement the resulting sections.

I built /deep-implement because after I'd automated my planning workflow through /deep-plan, I found myself executing the same steps over and over to actually implement the produced section files. Why not have Claude orchestrate it for me?

/deep-implement keeps the human in the loop through code review and managing context. In the future /deep-implement will look to provide even more automation.

TL;DR

Table of Contents

- Overview
- The Deep Trilogy
- Why deep-implement?
- When to Use
- Quick Start
- How It Works
- Installation
- Usage
- Workflow Steps
- Output Files
- Requirements
- Best Practices
- Troubleshooting
- Testing
- Project Structure
- Contributing

Overview

deep-implement orchestrates a disciplined implementation workflow:

For each section from /deep-plan, the plugin:
- Implements with TDD: Write tests first, then implementation
- Runs Code Review: A dedicated subagent reviews staged changes
- Interviews You: Triage findings, get your input on real decisions
- Updates Section Docs: Records what was actually built back into the section…