Explain MTHDS bundles

Analyze and explain existing MTHDS method bundles in plain language.

Process

Prerequisite: See CLI Prerequisites

Step 1: Read the .mthds File

Read the entire bundle file to understand its structure.

Step 2: Identify Components

List all components found in the bundle:

• Domain: the [domain] declaration

• Concepts: all [concept.*] blocks — note which are custom vs references to native concepts

• Pipes: all [pipe.*] blocks — identify the main pipe and sub-pipes

• Main pipe: declared in [bundle] section

Step 3: Trace Execution Flow

Starting from the main pipe, trace the execution path:

• For PipeSequence: follow the steps array in order

• For PipeBatch: identify batch_over and batch_as , then the inner pipe

• For PipeParallel: list all branches

• For PipeCondition: map condition → pipe for each branch

• For PipeLLM / PipeExtract / PipeImgGen / PipeFunc: these are leaf operations

Step 4: Present Explanation

Structure the explanation as:

• Purpose: one-sentence summary of what the method does

• Inputs: list each input with its concept type and expected content

• Output: the final output concept and what it contains

• Step-by-step flow: walk through execution in order, explaining what each pipe does

• Key concepts: explain any custom concepts defined in the bundle

Step 5: Generate Flow Diagram

Create an ASCII diagram showing the execution flow:

[input_a, input_b] | main_sequence ├── step_one (PipeLLM) → intermediate_result └── step_two (PipeExtract) → final_output

Adapt the diagram style to the method structure (linear, branching, batched).

Step 6: Optional — Validate

If the user wants to confirm the method is valid:

mthds-agent pipelex validate <file>.mthds -L <bundle-dir>/

Step 7: Optional — Visual Graph

For an interactive visual graph, suggest running the method with /run using real inputs:

mthds-agent pipelex run pipe <bundle-dir>/

This produces an interactive HTML visualization (live_run.html ) next to the bundle alongside the execution results (graph is generated by default).

Reference

• CLI Prerequisites — read at skill start to check CLI availability

• Error Handling — read when CLI returns an error to determine recovery

• MTHDS Agent Guide — read for CLI command syntax or output format details

• MTHDS Language Reference — read for concept definitions and syntax

• Native Content Types — read when explaining what data flows through pipes (e.g., what attributes Page or Image content carries)