ddw-ejectlisted

# Skill: /ddw-eject ## Description Installed as a plugin, the method lives outside your repository — nothing of DDW's is in your tree, which is what you want most of the time. **This copies it in.** That matters the moment you want to change something. A pipeline you cannot edit is a pipeline you have to accept whole, and the whole argument of this framework is that you should be deciding which parts of it earn their cost in *your* project. Editing the plugin would change every project you have; editing `.ddw/` in your repo changes this one. **The repo wins.** Every hook resolves the method as `.ddw/` first, the plugin second, so the moment this skill finishes there is nothing else to switch on. Your copy is the one that runs. ## When it is worth doing - You want to **remove a phase or a gate** your project does not need. - You want to **add a rule of your own**, or edit the wording of one that does not fit your domain. - You want the pipeline **versioned with the project**, so a change to it lands in a commit and shows up in review like any other decision. - Your team wants a teammate who clones the repo to get **exactly your pipeline**, not the current upstream default. If none of those apply, do not do this. The plugin updating itself is a real benefit, and you give it up here — see the trade below. ## Inputs - The plugin's method directory (`${CLAUDE_PLUGIN_ROOT}/ddw`, or the equivalent for your tool). - The repository root. ## Execution Protocol 1. **Check