Skip to main content

The Problem

Every session, your agents discover things:
  • Bugs and how to fix them
  • Patterns that work well
  • Approaches that failed
  • Tips that save time
Without capturing these, the next session starts from scratch. You rediscover the same things. Knowledge doesn’t compound.

The Learning Loop

Each captured insight makes future sessions smarter.

Capturing Learnings

Categories

Viewing Learnings

Storage

Learnings are stored in markdown at .agents/memory/<squad>/shared/learnings.md:

Auto-Tagging

The CLI automatically extracts tags from your insights:
Recognized patterns: auth, api, bug, perf, ux, test, db, deploy

Session Integration

Stop Hook

Add to .claude/settings.json to prompt for learnings at session end:

The /squads-learn Skill

When you run squads init, it creates a skill that Claude can invoke:
Claude will auto-invoke this skill when:
  • Finishing a task
  • Fixing a bug
  • Discovering a pattern
  • Learning something worth remembering

Best Practices

Don’t wait until end of session. Capture learnings as they happen.
“API is slow” → “API calls over 100 items trigger rate limiting, batch at 50”
“Use pnpm” → “Use pnpm instead of npm - 40% faster installs in CI”
Use --tags for learnings you’ll want to find later.

The Compounding Effect

A 30-second squads learn call can save hours of re-discovery.

Next Steps

Using Memory

Memory for current state

CLI Reference

All learn commands