trajectory-lineage

Trajectory And Lineage

Version Compatibility

Reference examples assume recent stable releases of the preferred tools, especially scanpy and the other tools listed below.

Before using code or command patterns, verify installed versions match the environment:

• Python: python -c "import <module>; print(<module>.__version__)"
• CLI: <tool> --version
• If signatures differ, inspect the installed help or API and adapt the pattern instead of retrying unchanged.

Overview

Workflow for pseudotime, lineage branching, and state-transition analysis in single-cell data.

When To Use This Skill

• use when the user asks for pseudotime, lineage branching, or developmental progression
• use when the single-cell object already has a coherent embedding and annotations
• use when dynamic gene programs or branch-specific markers are needed

Quick Route

• If the input is raw or minimally processed data, start with validation and QC before any modeling.
• If the input is already processed, skip directly to the first workflow step that matches the user goal.
• If the user asks for a biological conclusion, always produce at least one QC or confidence artifact alongside the final result.

Progressive Disclosure

• Read references/technical_reference.md when you need deeper tool-selection rules, environment adaptation notes, or extra validation guidance.
• Keep SKILL.md as the main execution path and load the reference file only when the task or failure mode needs the extra detail.

Default Rules

• Prefer Python-first workflows unless the task explicitly requires something else.
• Keep intermediate and final outputs separated.
• Record software versions, reference builds, and key parameters when they affect interpretation.
• Favor reproducible tables and figures over one-off interactive-only outputs.

Expected Inputs

• processed single-cell object
• cluster labels
• optional time or perturbation metadata

Expected Outputs

• pseudotime assignments
• branch or lineage states
• dynamic gene programs