Packs

Optional overlays shipped in the same npm package. Not copied on a default core install.

Not sure which packs you need? Each pack page starts with a Do I need this pack? flowchart — start with Spec and Stacks if you are new, then add integrations only when you feel the gap.

Install

npm

# First scaffold
npx create-lean-agent-kit@latest . --with spec,stacks

# Existing install
npx create-lean-agent-kit@latest . --enable-pack practice,caveman

# Agent skill
# Read .agent/skills/leanagentkit-enable-pack.md and follow it.

pnpm

# First scaffold
pnpm dlx create-lean-agent-kit@latest . --with spec,stacks

# Existing install
pnpm dlx create-lean-agent-kit@latest . --enable-pack practice,caveman

# Agent skill
# Read .agent/skills/leanagentkit-enable-pack.md and follow it.

yarn

# First scaffold
yarn dlx create-lean-agent-kit@latest . --with spec,stacks

# Existing install
yarn dlx create-lean-agent-kit@latest . --enable-pack practice,caveman

# Agent skill
# Read .agent/skills/leanagentkit-enable-pack.md and follow it.

bun

# First scaffold
bunx create-lean-agent-kit@latest . --with spec,stacks

# Existing install
bunx create-lean-agent-kit@latest . --enable-pack practice,caveman

# Agent skill
# Read .agent/skills/leanagentkit-enable-pack.md and follow it.

Dependencies are resolved automatically (architecture, backlog, and git-lifecycle pull in spec).

Catalog

Id	Depends	Docs
spec	—	Spec
stacks	—	Stacks
practice	—	Practice
architecture	spec	Architecture
backlog	spec	Backlog.md
git-lifecycle	spec	Git lifecycle
trevor	—	Trevor
caveman	—	Caveman
authoring	—	Create skill
imaginary	—	Imaginary

Installed packs are recorded in .agent/.leanagentkit-version → installedPacks.

Prune

npm

npx create-lean-agent-kit@latest . --prune-to-core
npx create-lean-agent-kit@latest . --prune-to-core --keep-pack spec,stacks

pnpm

pnpm dlx create-lean-agent-kit@latest . --prune-to-core
pnpm dlx create-lean-agent-kit@latest . --prune-to-core --keep-pack spec,stacks

yarn

yarn dlx create-lean-agent-kit@latest . --prune-to-core
yarn dlx create-lean-agent-kit@latest . --prune-to-core --keep-pack spec,stacks

bun

bunx create-lean-agent-kit@latest . --prune-to-core
bunx create-lean-agent-kit@latest . --prune-to-core --keep-pack spec,stacks

Pack files are moved to .leanagentkit-backup/<timestamp>-prune/, not deleted forever. That can include pack memory such as PROGRESS.md / reminders when those packs are removed; core ACTIVE_CONTEXT and LEARNINGS stay. User copies of pack config (.leanagentkit/<pack>.yml, derived from each pack's .yml.example) are archived with the removed pack — --keep-pack leaves that pack's config in place; --upgrade still preserves all user YAML. User-authored specs under docs/specs/ are left in place. After prune, review AGENTS.md §7 — it is preserved and may still list removed packs.

Dependencies are auto-installed (e.g. --enable-pack backlog also installs spec). Re-enable packs with --enable-pack.

practice

See the dedicated Practice page for guardrail skills (review, debug, TDD, security, …), always-on vs conditional detection, and whether you need the pack.