| name | pipelex-edit |
| description | Edit an existing MTHDS method bundle (.mthds files). Use when the user says "change this pipe", "update the prompt", "rename this concept", "rename this pipe", "change the model", "tweak the instructions", "modify the method", "add a step", "remove this pipe", "refactor this pipeline", or wants any modification to an existing .mthds bundle. Applies contract-preserving edits directly and routes structural or contract changes to /pipelex-design. |
Edit a MTHDS bundle
Modify an existing MTHDS method bundle. There are two classes of change; this skill applies the first and routes the second:
- Contract-preserving edits (this skill): prompt and instruction text,
description and system_prompt wording, model references, operator settings, and mechanical renames of pipes, concepts, or input variables. The method's structure — which pipes exist, how they wire, what each one takes and produces — stays the same.
- Structural or contract changes (route to
/pipelex-design): adding, removing, or rewiring steps; changing any pipe's inputs/output beyond a pure rename; reshaping a concept's structure; refactoring the flow. These propagate — the parent wiring, concept shapes, and contracts all move together — so they are design work: tell the user which pipe(s) the change touches and that /pipelex-design re-enters existing methods adaptively (a direct coherent edit for a fully understood shallow region, or signature-driven reopening for nested, uncertain, cross-module, or staged work), and stop. Never attempt a partial structural edit here.
Requirements — the Pipelex MCP tools
This skill proves every edit with the mthds_validate tool, served by the plugin's pipelex MCP server. It is required — never declare an edit done on the hook's silence alone: the hook's semantic-validation stage is fail-open (it is skipped without an API key), so the MCP verdict is the authoritative check.
