ed3d-plugins
A Claude Code plugin marketplace built around a research, plan, implement loop: from a rough idea to reviewed code in git
- 253 ★ on the repository
- Last commit
Broad access
Why this level
- Plugins install PreToolUse, PostToolUse and UserPromptSubmit hooks that see the agent's commands and prompts
- The execution loop commits to git and launches sub-agents with your session's permissions
- The repository is unmaintained, so security updates are not expected
Install
- Works in
Manual install
/plugin marketplace add https://github.com/ed3dai/ed3d-plugins.gitAdds the marketplace. Plugins are installed separately with /plugin install name@ed3d-plugins.
Access and checks
How we reviewBroad accessThe tool can change data, run commands or handle secrets.
- Plugins install PreToolUse, PostToolUse and UserPromptSubmit hooks that see the agent's commands and prompts
- The execution loop commits to git and launches sub-agents with your session's permissions
- The repository is unmaintained, so security updates are not expected
This is third-party code. Review the repository files before installing.
What it does
ed3d-plugins is a developer's personal marketplace, and Claude Code installs eleven plugins from it. The main one, ed3d-plan-and-execute, runs a task through a chain: /start-design-plan turns a rough idea into a design document committed to git, /start-implementation-plan splits it into phase files, and /execute-implementation-plan carries out the plan with review and commits. The other plugins support the loop. ed3d-basic-agents provides general-purpose agents on haiku, sonnet and opus, ed3d-research-agents searches code and the web, and ed3d-extending-claude teaches an agent to write plugins, commands, agents and skills. ed3d-house-style captures the author's opinions on code: Rust, TypeScript, React, Postgres, property-based testing. Hooks catch secret leaks, remind you to update CLAUDE.md before a commit and nudge the agent to use skills. Project requirements go into .ed3d/design-plan-guidance.md and .ed3d/implementation-plan-guidance.md, and /how-to-customize explains how. The author warns that the repository is no longer maintained because they moved away from Claude Code to another tool.
Who it is for. For Claude Code developers who want a strict order for large tasks and ready-made opinions on code, and can do without the author's support.
Good fit when
- A task spans several days and should be designed in a document first, then executed phase by phase with review
- The agent drifts from the original requirements midway and you need a loop that checks the design against the implementation
- The project needs shared rules for Rust, TypeScript, React or Postgres and you are happy to start from someone else's
- You want secret leaks caught in Bash commands and sensitive files before they run: ed3d-hook-security-hardening does that
- You write your own plugins or skills and want the ed3d-extending-claude set as a model
Not a fit when
- You need an actively maintained project: the author says the repository is not developed and newer changes go to a separate testing marketplace
- The task is small, a change to a couple of files: the three-stage loop with a design document and phases adds extra ritual
- Your agent is not Claude Code: the plugins, commands and hooks are written for it
- You disagree with the author's opinions on code: ed3d-house-style is called very opinionated and is offered as a reference
Example request
Run /start-design-plan and take me from the idea of exporting reports to CSV to a design document, then prepare a phased implementation planLimitations
- The repository is unmaintained because the author moved to another tool. Newer changes live in ed3d-plugins-testing.
- Plugins depend on each other: ed3d-basic-agents, ed3d-research-agents and ed3d-extending-claude are needed by the rest, and the ed3d-hook-skill-reinforcement hook requires ed3d-extending-claude.
- ed3d-session-reflection is marked experimental.
- The license is CC BY-SA 4.0 with share-alike terms, while code derived from obra/superpowers stays under MIT.
How to disable. Remove installed plugins with /plugin uninstall using a name like ed3d-plan-and-execute@ed3d-plugins, then drop the marketplace with /plugin marketplace remove ed3d-plugins. The .ed3d/ files in a project can be deleted by hand.
FAQ
How do I install ed3d-plugins in Claude Code?
Add the marketplace with /plugin marketplace add https://github.com/ed3dai/ed3d-plugins.git, then install what you need with a command like /plugin install ed3d-plan-and-execute@ed3d-plugins. The helper plugins ed3d-basic-agents, ed3d-research-agents and ed3d-extending-claude are expected by the rest.
How does the research-plan-implement loop work?
First /start-design-plan creates and commits a design document, then /start-implementation-plan writes a plan as phase files, and /execute-implementation-plan runs it with review and commits. The author believes this order reduces hallucination during planning.
How do I set rules for my own project?
Create .ed3d/design-plan-guidance.md and .ed3d/implementation-plan-guidance.md in the project and describe constraints, terminology and standards there. /how-to-customize prints the details.
How is ed3d-plan-and-execute related to Superpowers?
The plugin and part of ed3d-extending-claude grew out of obra/superpowers by Jesse Vincent and were heavily reworked. Some ed3d-house-style skills come from there as well, and property-based-testing builds on the Trail of Bits skills.
Is the project maintained?
No, the author states that they moved away from Claude Code and the repository is no longer maintained. They point to ed3d-plugins-testing for newer changes.
Discussion
No questions or reviews yet.
Related
PluginsA marketplace of 23 plugins for Claude Code: git and pull requests, code review, TDD, specs and delegation to other models
A Claude Code plugin marketplace by Frad LEE: Git and GitFlow, GitHub, refactoring, memory, research, image generation and interface work
Claude Code plugins: plan, work and review commands, subagents, hooks and writing skills in a practical minimalism spirit.
The ce plugin for Claude Code and Codex: eleven skills and four sub-agents for plans, review, tests, architecture and writing.
A marketplace of eight Claude Code plugins: session memory, research, commits, skill authoring and more.
A marketplace of 18 Claude Code plugins: access to blocked pages, second-model review, design systems from a site, research and planning
README in short
The README opens with a notice that the author no longer maintains the repository, then describes the main plugin and its three-command loop. A table lists eleven plugins with their purpose, followed by installation, folder structure, contributing, code attribution and license.