deep-implement
starsforks
How to install deep-implement?
piercelamb/deep-implement
$git clone https://github.com/piercelamb/deep-implementClaude Code plugin that implements code from /deep-plan sections with TDD, code review, and git workflow
README.md
| 1 |  |
| 2 | |
| 3 | # /deep-implement, a Claude Code plugin |
| 4 | |
| 5 |  |
| 6 |  |
| 7 |  |
| 8 |  |
| 9 |  |
| 10 | |
| 11 | > **Blog posts:** |
| 12 | > - [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 |
| 13 | > - [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 |
| 14 | |
| 15 | `/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. |
| 16 | |
| 17 | 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. |
| 18 | |
| 19 | 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. |
| 20 | |
| 21 | 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? |
| 22 | |
| 23 | `/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. |
| 24 | |
| 25 | ## TL;DR |
| 26 | ``` |
| 27 | /plugin marketplace add piercelamb/deep-implement |
| 28 | /plugin install deep-implement |
| 29 | /plugin enable deep-implement |
| 30 | /deep-implement @planning/sections/. |
| 31 | ``` |
| 32 | |
| 33 | ## Table of Contents |
| 34 | |
| 35 | - [Overview](#overview) |
| 36 | - [The Deep Trilogy](#the-deep-trilogy) |
| 37 | - [Why deep-implement?](#why-deep-implement) |
| 38 | - [When to Use](#when-to-use) |
| 39 | - [Quick Start](#quick-start) |
| 40 | - [How It Works](#how-it-works) |
| 41 | - [Installation](#installation) |
| 42 | - [Usage](#usage) |
| 43 | - [Workflow Steps](#workflow-steps) |
| 44 | - [Output Files](#output-files) |
| 45 | - [Requirements](#requirements) |
| 46 | - [Best Practices](#best-practices) |
| 47 | - [Troubleshooting](#troubleshooting) |
| 48 | - [Testing](#testing) |
| 49 | - [Project Structure](#project-structure) |
| 50 | - [Contributing](#contributing) |
| 51 | |
| 52 | ## Overview |
| 53 | |
| 54 | **deep-implement** orchestrates a disciplined implementation workflow: |
| 55 | |
| 56 | ``` |
| 57 | Read Section → TDD Implementation → Code Review → Interview → Commit → Next |
| 58 | ``` |
| 59 | |
| 60 | For each section from `/deep-plan`, the plugin: |
| 61 | - **Implements with TDD**: Write tests first, then implementation |
| 62 | - **Runs Code Review**: A dedicated subagent reviews staged changes |
| 63 | - **Interviews You**: Triage findings, get your input on real decisions |
| 64 | - **Updates Section Docs**: Records what was actually built back into the section file |
| 65 | - **Commits Atomically**: One commit per section with review trail |
| 66 | - **Tracks Progress**: Resume from any point after interruption |
| 67 | |
| 68 | By the end, you have production-ready code with a git history that tells a clear story—and section documents that serve as living documentation of what was actually built, not just what was planned. |
| 69 | |
| 70 | ## The Deep Trilogy |
| 71 | |
| 72 | This plugin is part of a three-plugin pipeline for turning ideas into production code: |
| 73 | |
| 74 | ``` |
| 75 | /deep-project (decompose) → /deep-plan (plan) → /deep-implement (build) |
| 76 | ``` |
| 77 | |
| 78 | ``` |
| 79 | ┌───────────────────────────────────────────────────────────────────┐ |
| 80 | │ THE DEEP TRILOGY │ |
| 81 | │ From Vague Idea to Production Code │ |
| 82 | ├───────────────────────────────────────────────────────────────────┤ |
| 83 | │ │ |
| 84 | │ "I want to build a SaaS platform" │ |
| 85 | │ │ │ |
| 86 | │ ▼ │ |
| 87 | │ ┌─────────────────────────────────────┐ │ |
| 88 | │ │ /deep-project │ │ |
| 89 | │ └─────────────────────────────────────┘ │ |
| 90 | │ │ │ │ │ |
| 91 | │ ▼ ▼ ▼ │ |
| 92 | │ ┌─────────┐ ┌─────────┐ ┌─────────┐ │ |
| 93 | │ │ 01-auth │ │ 02-bill │ │ ... │ │ |
| 94 | │ │ spec.md │ │ spec.md │ │ │ │ |
| 95 | │ └─────────┘ └─────────┘ └─────────┘ │ |
| 96 | │ │ │ │ │ |
| 97 | │ ▼ ▼ ▼ │ |
| 98 | │ ┌─────────┐ ┌─────────┐ ┌─────────┐ │ |
| 99 | │ │ /deep- │ │ /d |
People who liked this also viewed
6 picksType
- revdiffTUI for reviewing diffs, files, and documents with inline annotationsWorkflowsJul 2026
- cc-plugin-codexAn open-source plugin that runs inside Codex and lets you use Claude Code and Claude models for review, rescue, and tracked background workflows.WorkflowsJul 2026
- correctlessThe agent that writes the code never reviews it. Spec-driven TDD with agent separation, adversarial QA, and dynamic rigor for Claude Code.WorkflowsJul 2026
- tornadoReview by codex, develop by claude-codeWorkflowsApr 2026
- ai-pr-reviewA robust GitHub Actions workflow that provides AI-powered code reviews using Amp or Claude CodeWorkflowsAug 2025
- claude-git-pr-skillProfessional GitHub PR review skill for Claude Code with pending reviews, code suggestions, and user approval workflowWorkflowsDec 2025
