Inspecting workflow details from the CLI
========================================

Use ``raft available-workflows`` to list workflow groups, then narrow to one
workflow and input type:

.. code-block:: console

  $ raft available-workflows
  $ raft available-workflows --workflow lens
  $ raft available-workflows --workflow lens --species human --input fastqs

The default output is a compact summary with profiles, steps, default
parameter count, and the next command shapes. It also notes that setup can take
a few minutes while RAFT fetches workflow modules. The generated ``raft run``
commands omit ``--manifest`` because it is optional for new projects; add
``--manifest <MANIFEST>`` when you already have a manifest file.

.. code-block:: console

  $ raft available-workflows \
      --workflow lens \
      --species human \
      --input fastqs

Use ``--details`` when you need the full default parameter table:

.. code-block:: console

  $ raft available-workflows \
      --workflow lens \
      --species human \
      --input fastqs \
      --details

If you need module-derived alternate tool choices, add
``--show-alternate-tools``:

.. code-block:: console

  $ raft available-workflows \
      --workflow lens \
      --species human \
      --input fastqs \
      --show-alternate-tools

Use ``--json`` when scripting workflow discovery:

.. code-block:: console

  $ raft available-workflows \
      --workflow lens \
      --species human \
      --input fastqs \
      --json

The JSON form is compact by default. Use ``--details --json`` for the larger
payload with default parameter values. The compact summary includes command
shapes for creating a project with ``raft run``.