Foundry
Home Pipeline

WORKFLOW BRIEF → GALAXY

Consume an expert-reviewed, unchanged Workflow Brief directly through the Galaxy design and implementation chain.

draft target/galaxyjourney/build-from-plan

Phases

/ subway map 11 phases
  1. workflow-brief-to-galaxy-interface
  2. workflow-brief-to-galaxy-data-flow
  3. compare-against-iwc-exemplar
  4. workflow-brief-to-galaxy-template
  5. advance-galaxy-draft-step loop
  6. branch test-data-resolution
    1. find-test-data
    2. user-supplied
  7. workflow-brief-to-galaxy-test-plan
  8. implement-galaxy-workflow-test
  9. validate-galaxy-workflow
  10. run-workflow-test
  11. debug-galaxy-workflow-output

Run this pipeline

/ stop-gap harness

Run this pipeline today via its assembled harness skill pipeline-workflow-brief-to-galaxy — install once (run guide), then select it in your runtime: 

Claude:      /foundry-skills:pipeline-workflow-brief-to-galaxy
Codex:       $pipeline-workflow-brief-to-galaxy
Antigravity: /pipeline-workflow-brief-to-galaxy

Each run gets its own ./<run-slug>/ working directory so artifacts stay namespaced and a second run won't clobber the first — the harness sets this up first (phase detail).

phases
11
auto casts
10
manual
1
loops
1

WORKFLOW BRIEF → GALAXY

A reviewed brief is the entry point, including a hand-authored brief. The harness checks declared blockers, review, and current environment readiness before any design. Galaxy design Molds consume the brief directly; a retained source summary remains optional evidence rather than an intermediate authority.

The input brief remains unchanged. open-requirements.ledger.yml records durable workflow discoveries, decisions, obligations, and proposed brief changes; ordinary phase progress remains harness state. Only a separate expert editing step can change scope or requirements. A required brief change stops implementation and returns to that editing step.

Source-to-brief journeys remain independently usable so they can finish with an honest blocked draft. The paper and interview direct journeys remain separate, freeform-summary-driven routes; planning is explicit composition of a source-to-brief producer with this brief-driven implementation spine. This initial implementation route does not yet dispatch to the specialized Nextflow reference-data and test-translation chain.