Is this a legit way of using a nextflow pipeline as a module in another pipeline? And if so, isn't then pipeline "chaining" already possible if doing that? https://github.com/assemblerflow/flowcraft This has a bioconda recipe with nextflow requirement:

{% set name = "assemblerflow" %}
{% set version = "1.1.0.post3" %}

package:
  name: '{{ name|lower }}'
  version: '{{ version }}'

source:
  url: <https://pypi.io/packages/source/{{> name[0] }}/{{ name }}/{{ name }}-{{ version }}.tar.gz
  sha256: b0390727602e90dad1c3afa8dd408e5c30471a0f6d35b323989e9df4e8aa70fb

build:
  noarch: python
  number: 2
  entry_points:
    - assemblerflow = assemblerflow.assemblerflow:main
  script: {{ PYTHON }} -m pip install --no-deps --ignore-installed .

requirements:
  host:
    - python >=3
    - pip
  run:
    - python >=3
    - argparse
    - jinja2
    - nextflow >=0.27

test:
  imports:
    - assemblerflow
    - assemblerflow.generator
    - assemblerflow.generator.components
    - assemblerflow.templates
  commands:
    - assemblerflow --help

about:
  home: <https://github.com/ODiogoSilva/assemblerflow>
  license: GPL3
  license_family: GPL3
  license_file: LICENSE
  summary: A Nextflow pipeline assembler for genomics. Pick your modules. Assemble them. Run the pipeline.
  doc_url:  <http://assemblerflow.readthedocs.io/en/latest/>
  dev_url: <http://assemblerflow.readthedocs.io/en/latest/>

extra:
  recipe-maintainers:
    - odiogosilva

and then can be run as a cli tool like this:

flowcraft build ..

as far as I understand.