How to Use Lineage

This page explains the simple flow.

1. Create Or Receive A Package

A Lineage package is a normal folder with a lineage.yaml manifest.

package/
├── lineage.yaml
├── skills/
├── workflows/
├── agents/
├── policies/
├── references/
└── adapters/

These folders are plain on purpose. You should be able to inspect what a package contains.

lineage init user

For a named workspace:

lineage init workspace <name>

lineage package init resume-workflow

Then add the package files, skills, workflows, references, policies, or adapters that belong to that environment.

From the project where you want to use the package:

lineage enable ./resume-workflow

This records the package in .lineage/config.yaml.

lineage run claude --dry-run
lineage run codex --dry-run

The dry run shows which provider, project config, and packages Lineage would use.

Lineage can install shims so normal provider commands enter Lineage first:

lineage install-shims

Then put the shim directory before existing provider binaries in PATH.

Do not package secrets, credentials, provider login state, private prompts, .env values, or machine-local cache files.

If a workflow needs receiver-specific values, package a template or setup prompt instead.