| name | pipeline-cwl-to-galaxy |
| description | Path from a CWL Workflow to a Galaxy gxformat2 workflow — orchestrates the Foundry skills of the CWL → GALAXY pipeline in order, in a per-run working directory. |
pipeline-cwl-to-galaxy
Harness for the CWL → GALAXY Foundry pipeline. Runs the constituent skills in order inside a single per-run working directory. Assembled from content/pipelines/cwl-to-galaxy/index.md (revision 2) — regenerate with foundry-build assemble-pipeline cwl-to-galaxy if the pipeline changes; do not hand-edit.
When To Use
- Path from a CWL Workflow to a Galaxy gxformat2 workflow. Lighter upstream extraction.
Bootstrap (install these CLIs first)
Install the harness CLIs every constituent skill invokes before driving the pipeline. Deduped across all phases; bioinformatics tools the constructed workflow installs are out of scope (the discovery phase pins those).
Run options
Optional flags, given as leading arguments. Strip any you recognize; treat the remaining positional argument as the run slug. Both default off and compose.
--use-subagents — run each cast phase in its own subagent to keep this orchestrator's context small. For each phase whose skill is cast, spawn a subagent, tell it the run directory and to invoke the named skill with every default filename prefixed by ./<run-slug>/, and have it return a short report (artifacts written, assumptions, status) rather than its full transcript; carry only that report forward. A cast loop phase runs one subagent per iteration — each advances a single step and returns its done-signal, and you inspect that signal to decide whether to spawn the next iteration. Branch phases run their whole fallback chain in one subagent. MANUAL (un-cast) phases are never delegated — including MANUAL loop phases — so handle those yourself regardless of the per-iteration rule above.--checkpoint — commit after every phase so the run directory's git history is a per-step record (a data source for workflow-implementation visualizations). When set, git init ./<run-slug>/ during working-directory setup — this is a standalone per-run repo; do not add it to any surrounding repo you are working inside. Then after each phase's artifact is confirmed run git -C ./<run-slug>/ add -A && git -C ./<run-slug>/ commit -m "phase <n>: <skill>". Loop phases commit once per iteration (phase <n> step <k>: <skill>); for a MANUAL loop, commit once per by-hand step. With --use-subagents, the subagent does the work and returns; you make the commit.
Working directory (do this first)
Every constituent skill writes fixed filenames to its working directory. To keep one run's artifacts namespaced and avoid clobbering a prior run (foundry#282):
- Pick a run slug — use the harness argument if given; else ask the user for a short project name up front (the directory must exist before phase 1 writes its first artifact, so don't wait for a source title); else default
cwl-to-galaxy-run.
- Create
./<run-slug>/ in the current directory. If it exists, suffix -2, -3, … . If invoked with --checkpoint, run git init ./<run-slug>/ now (see Run options).
- Run every skill invocation below with
./<run-slug>/ as its working directory: prefix every default input and output filename with ./<run-slug>/ when you invoke the skill. The skills preserve their declared basenames and honor a harness-supplied directory; you supply the prefix on both reads and writes, so each phase finds the prior phase's output and nothing lands in the repo root.
Announce the chosen directory before starting.
Pipeline
Run these phases in order. After each, confirm the expected artifact exists in the run directory before advancing.
- summarize-cwl — invoke the
summarize-cwl skill. Validate and normalize a CWL Workflow tree, then emit a lightweight structured summary for downstream Galaxy translation.
- cwl-summary-to-galaxy-interface — invoke the
cwl-summary-to-galaxy-interface skill. Map a CWL summary into a Galaxy workflow interface design brief.
- cwl-summary-to-galaxy-data-flow — invoke the
cwl-summary-to-galaxy-data-flow skill. Translate a CWL summary into a Galaxy data-flow design brief.
- compare-against-iwc-exemplar — invoke the
compare-against-iwc-exemplar skill. Find nearest IWC exemplar(s) and surface a structural diff against the upstream Galaxy design briefs to guide template authoring.
- cwl-summary-to-galaxy-template — invoke the
cwl-summary-to-galaxy-template skill. gxformat2 skeleton with per-step TODOs from a CWL summary and prior Galaxy design briefs.
- advance-galaxy-draft-step (loop) — invoke the
advance-galaxy-draft-step skill, once per step. It owns its own endstate oracle (gxwf draft-next-step) and concretizes one drafty step per call; re-invoke until it reports draft: false, then it extracts the concrete galaxy-workflow.gxwf.yml (via gxwf draft-extract) and continues.
- test-data-resolution (branch) — resolve in order; stop at the first that yields acceptable output:
- Try
cwl-to-test-data — Resolve a CWL workflow's own declared test cases into Galaxy workflow test-data refs.
- Otherwise try
find-test-data — Search IWC fixtures and public sources for test data matching a data-flow shape.
- user-supplied — if nothing above yields acceptable output, ask the user to supply it directly.
- cwl-test-to-galaxy-test-plan — MANUAL —
cwl-test-to-galaxy-test-plan is not yet cast. Translate CWL test fixtures into a Galaxy workflow test plan. Do this by hand and confirm before continuing.
- implement-galaxy-workflow-test — invoke the
implement-galaxy-workflow-test skill. Assemble Galaxy workflow test fixtures and assertions.
- validate-galaxy-workflow — invoke the
validate-galaxy-workflow skill. Run terminal gxwf validation on an assembled Galaxy workflow and classify workflow-level failures.
- run-workflow-test — invoke the
run-workflow-test skill. Execute a workflow's tests via Planemo; emit structured pass/fail and outputs.
- debug-galaxy-workflow-output — invoke the
debug-galaxy-workflow-output skill. Triage failing Galaxy run outputs; classify the failure surface and capture evidence before recommending repairs.
Done
Report the final artifacts in ./<run-slug>/ and any phases handled manually (marked MANUAL above).
Notes
- Do not re-implement any skill's internal logic here; this harness only sequences and routes.
- Carry unresolved assumptions forward as notes rather than inventing missing inputs.
