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.
> /plugin marketplace add piercelamb/deep-implement> /plugin install deep-implement@piercelamb-plugins
What's inside
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.
/plugin marketplace add piercelamb/deep-implement
/plugin install deep-implement
/plugin enable deep-implement
/deep-implement @planning/sections/.
deep-implement orchestrates a disciplined implementation workflow:
Read Section → TDD Implementation → Code Review → Interview → Commit → Next
For each section from /deep-plan, the plugin:
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.
This plugin is part of a three-plugin pipeline for turning ideas into production code:
/deep-project (decompose) → /deep-plan (plan) → /deep-implement (build)
┌───────────────────────────────────────────────────────────────────┐
│ THE DEEP TRILOGY │
│ From Vague Idea to Production Code │
├───────────────────────────────────────────────────────────────────┤
│ │
│ "I want to build a SaaS platform" │
│ │ │
│ ▼ │
│ ┌─────────────────────────────────────┐ │
│ │ /deep-project │ │
│ └─────────────────────────────────────┘ │
│ │ │ │ │
│ ▼ ▼ ▼ │
│ ┌─────────┐ ┌─────────┐ ┌─────────┐ │
│ │ 01-auth │ │ 02-bill │ │ ... │ │
│ │ spec.md │ │ spec.md │ │ │ │
│ └─────────┘ └─────────┘ └─────────┘ │
│ │ │ │ │
│ ▼ ▼ ▼ │
│ ┌─────────┐ ┌─────────┐ ┌─────────┐ │
│ │ /deep- │ │ /deep- │ │ ... │ │
│ │ plan │ │ plan │ │ │ │
│ └─────────┘ └─────────┘ └─────────┘ │
│ │ │ │ │ │ │ │
│ ▼ ▼ ▼ ▼ ▼ ▼ │
│ ┌────┐┌────┐┌────┐┌────┐┌────┐┌─────────┐ │
│ │ 01 ││ 02 ││ 01 ││ 02 ││ 03 ││ ... │ │
│ └────┘└────┘└────┘└────┘└────┘└─────────┘ │
│ │ │ │ │ │ │ │
│ └─┬──┘ └──┬──┴────┘ │ │
│ │ │ │ │
│ ▼ ▼ ▼ │
│ ┌─────────┐┌─────────┐ ┌─────────┐ │
│ │ /deep- ││ /deep- │ │ ... │ ◀── YOU ARE HERE │
│ │implement││implement│ │ │ │
│ └─────────┘└─────────┘ └─────────┘ │
│ │ │ │ │
│ ▼ ▼ ▼ │
│ ┌─────────┐┌─────────┐ ┌─────────┐ │
│ │ auth ││ billing │ │ ... │ │
│ │ code ││ code │ │ │ │
│ └─────────┘└─────────┘ └─────────┘ │
│ │ │ │ │
│ └──────────┴──────────────────┘ │
│ │ │
│ ▼ │
│ Production Codebase │
│ │
└───────────────────────────────────────────────────────────────────┘
| Plugin | Purpose | Input | Output |
|---|---|---|---|
/deep-project | Decompose | Vague requirements | Focused spec files |
/deep-plan | Plan | Spec file | Section files with TDD |
/deep-implement | Build | Section files | Production code |
Where to start?
/deep-project/deep-plan/deep-implementYou: "Claude, implement this plan"
Claude: *implements everything at once*
Result: Massive PR, unclear history, missed requirements discovered too late
You: "/deep-implement @planning/sections/."
deep-implement: Section 1 → TDD → Review → Commit → Section 2 → ...
Result: Atomic commits, code review at each step, clear progress tracking
Benefits:
Use deep-implement when:
/deep-planSkip deep-implement when:
Prerequisite: You need section files from
/deep-plan. If you don't have them, run/deep-plan @your-spec.mdfirst.
1. Point to your sections directory:
/deep-implement @planning/sections/.
2. Confirm target directory (where code will be written)
3. Follow the workflow for each section:
That's it. Each section gets implemented, reviewed, and committed before moving to the next.
Token Note: This workflow creates a detailed task list. Expand your terminal window to avoid UI flickering from the progress display.
View @piercelamb’s profileBlog posts: The Deep Trilogy - How the three plugins work together What I Learned - Technical lessons from plugin development /deep-project transforms vague, high-level project requirements into well-scoped planning units through AI-assisted interview and
@piercelambFAQ
deep-implement is a Claude Code plugin with 1 hand-picked skill for development work, indexed on Flowy. Install it with the command on its page. It includes deep-implement. Its skills do not fire on their own yet. Request auto-invocation to have Flowy route them as you prompt. Free and open source.
Is this plugin yours?
Claim it with GitHubSubmit a pluginPromote it