Lineage

Package how
your agents work.

Bundle skills, workflows, agents, and policies into one package. Anyone can inspect it, enable it, and run it through their own Claude or Codex — nothing hidden, nothing replaced.

$curl -fsSL https://agenticlineage.vercel.app/install.sh | sh
Open SourceMITGo runtime

What is Lineage?

Lineage packages complete behavior.

A prepared agent package travels as one local environment: skills, workflows, agents, policies, references, setup material, and provider entrypoints can be bundled, inspected, enabled, and launched from the receiver's machine.

7Package folders
1Manifest
2Current adapters
resume-workflow@0.1.0lineage.yaml
workflow
resume-review
skill
resume-review
step
truth + voice
check
role fit
package
resume-workflow
Claude
Codex

Package contents

Everything in its place.

A Lineage package is a normal folder with a lineage.yaml manifest. The receiver should be able to open it and understand what will be enabled.

Skills

Reusable expertise and capabilities.

Agents

Workers, roles, tools and permissions.

Workflows

Ordered steps, checks and validations.

Policies

Rules that keep package behavior bounded.

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

Current runtime flow

Prepare. Enable. Preview.

Lineage currently focuses on reliable local package creation, enablement, launch planning, and provider shim entry.

$ lineage init user
$ lineage init workspace my-project
$ lineage package init resume-workflow
$ lineage enable ./resume-workflow
$ lineage run claude --dry-run
$ lineage run codex --dry-run
$ lineage install-shims
  1. Package safely with lineage.yaml
  2. Inspect before enabling locally
  3. Preview the provider launch plan

Provider adapters

Works around
your tools.

Lineage does not replace the agent provider. It sits around local commands and keeps provider-specific behavior behind clear adapter boundaries.

Read architecture ->
Claude logo

Claude

Local provider adapter for Claude command workflows.

In repo

Codex

Local provider adapter for Codex command workflows.

In repo

Real example package

Resume workflow.

The repo includes a resume-focused package example with one exported workflow and one required skill.

Open example ->
FilePurposeFrom repoStatus
lineage.yamlDeclares resume-workflow, version 0.1.0, exports resume-review.examples/Present
skills/resume-reviewReviews resume material for clarity, evidence, role fit, and missing details.examples/Present
workflows/resume-reviewConfirms target role, finds missing evidence, suggests truthful revisions, and summarizes.examples/Present
references/source-notes-template.csvTemplate for receiver-provided local source notes.examples/Present

Community

Built in the open.

Contribute focused, testable changes. Discuss package safety, adapters, and workflow distribution in public.

Wiki

Design docs, specifications and deep dives.

Explore ->

Discussions

Ask questions, share ideas and help others.

Join ->

GitHub

Source code, issues, releases and contribution flow.

View ->

Why a package, not a prompt

Distribute the process, not just the prompt.

A workflow is more than a skill. It's the order you run things in, the checkpoints, the validation gates. Lineage packages that whole process, so whoever you hand it to runs it the way you built it, not a rebuilt guess.

Read the Wiki ->Join Discussions ->