Explain MTHDS bundles

Process

Step 1: Read the .mthds File

Step 2: Identify Components

• 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

1. For PipeSequence: follow the

   steps

   array in order
2. For PipeBatch: identify

   batch_over

   and

   batch_as

   , then the inner pipe
3. For PipeParallel: list all branches
4. For PipeCondition: map condition → pipe for each branch
5. For PipeLLM / PipeExtract / PipeImgGen / PipeFunc: these are leaf operations

Step 4: Present Explanation

1. Purpose: one-sentence summary of what the method does
2. Inputs: list each input with its concept type and expected content
3. Output: the final output concept and what it contains
4. Step-by-step flow: walk through execution in order, explaining what each pipe does
5. Key concepts: explain any custom concepts defined in the bundle

Step 5: Generate Flow Diagram

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

Step 6: Optional — Validate

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

Step 7: Optional — Visual Graph

/run

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

live_run.html

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)