executing-plans
executing-plans
Use when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available
trio-callingPlans DeepTrio trio and duo variant-calling workflows with child and parent inputs, per-sample VCF/gVCF outputs, and GLnexus merge handoff.
Independent GitHub snapshot · Automated classification · Original documentation governs
Use this sub-skill when a user needs DeepTrio family calling for a child with one or two parents. It covers Docker/Bazel-style run_deeptrio command planning, duo behavior when one parent is absent, model-type choice, per-sample output planning, gVCF merge handoff, and family-specific troubleshooting.
run_deeptrio workflows, trio/duo sample planning, child/parent output naming, gVCF planning, GLnexus handoff, and sex-chromosome parent-selection caveats.run_deepvariant germline calling to the germline-calling sub-skill.pangenome-aware-calling sub-skill.make_examples, call_variants, postprocess_variants, sharded TFRecords, and extra-args internals to the pipeline-stages sub-skill.hap.py, RTG, and visualization to the analysis-visualization sub-skill.child, parent1, and parent2; duo has child and exactly one parent.--model_type from WGS, WES, PACBIO, or ONT according to the sequencing data and image/model availability.scripts/deeptrio_command_builder.py to validate the plan and print a reviewable command without executing Docker, DeepTrio, or GLnexus.references/workflows.md, references/deeptrio-flags.md, and references/troubleshooting.md for command patterns, flag contracts, and recovery steps.The helper is a command planner only:
python scripts/deeptrio_command_builder.py --help
It validates child/parent flag groups, makes duo mode explicit by omitting every parent2 flag, warns about WES regions and long-read candidate partitioning, and can emit a GLnexus handoff command when a complete gVCF set is present.
Do not run Docker, GLnexus, network downloads, GPU jobs, or native DeepTrio tests without explicit user approval and real user-provided genomics inputs. Treat generated commands as plans until the user confirms the runtime environment, container mounts, and data paths.