agentleFS
Sach1ngSach1ng/PM-operating-OS/skills/continual-learning/SKILL.md

continual-learning

Skill3 starsChanged 18 days agoMITView on GitHub

Mine chat transcripts for decisions, exec updates, strategy shifts, feedback themes, and user preferences. Write structured entries to memory/, then update AGENTS.md with curated preferences and facts. Cursor-first ingestion pipeline.

8 other projects use a version of this, 2 of them edited.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

6 rules. 0 are common, 6 are distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 5 edited versions we read keep these.

  • 6

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    After a batch of important conversations (strategy sessions, PRD reviews, planning)

    line 14
  2. Distinctive:

    After writing to memory, update the Learned sections in AGENTS.md:

    line 121
  3. Distinctive:

    Update matching bullets in place (don't duplicate)

    line 127
  4. Distinctive:

    Add only net-new bullets

    line 128
  5. Distinctive:

    Remove entries for files that no longer exist on disk

    line 137
  6. Distinctive:

    Keep an item only if all are true:

    line 141

“Common” is measured: kept by at least 6 in 10 of the 5 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Continual Learning

Ingestion pipeline for PM-OS memory. Reads chat transcripts, classifies what it finds, writes structured entries to memory/, and updates AGENTS.md with curated preferences and facts. Cursor-first.

When to Use

  • "Run continual learning" / "mine my chats" / "update memory"
  • On a schedule (e.g. end of week) to keep memory current
  • After a batch of important conversations (strategy sessions, PRD reviews, planning)

Inputs

  • Transcript root: ~/.cursor/projects/<workspace-slug>/agent-transcripts/
  • Existing memory: AGENTS.md + memory/ subdirectories
  • Incremental index: .cursor/hooks/state/continual-learning-index.json

Workflow

1. Load state

  1. Read existing AGENTS.md.
  2. Load incremental index (if present).
  3. Discover transcript files. Process only:
    • new files not in the index, or
    • files whose mtime is newer than the indexed mtime.

2. Extract and classify

For each new/changed transcript, extract high-signal items and classify each into one of these categories:

CategoryWhat to look forWrite to
DecisionUser made or confirmed a product decision (PRD approval, scope change, launch/kill, prioritization shift, stakeholder alignment)memory/decisions/
Exec updateUser drafted or discussed an executive status update, SLT summary, or program updatememory/exec-updates/
Strategy shiftUser discussed or changed strategic direction, pillars, positioning, or goalsmemory/strategy-reviews/
Feedback insightUser analyzed customer feedback, VOC themes, or support trendsmemory/feedback/
User preferenceRecurring correction or stated broad rule about how the AI should behaveAGENTS.md → Learned User Preferences
Workspace factDurable fact about the workspace, tools, file paths, or workflowsAGENTS.md → Learned Workspace Facts

Skip: one-off task instructions, transient details (branch names, commit hashes, temp errors), secrets/tokens/credentials, and anything not actionable in future sessions.

3. Write to memory

For each extracted item (except preferences/facts), write a structured entry to the appropriate memory/ subdirectory:

Decisions → memory/decisions/YYYY-MM-DD_short-slug.md

# [Decision title]

**Date:** YYYY-MM-DD
**Source:** continual-learning (transcript extraction)
**Type:** [PRD approval | Scope change | Launch/Kill | Prioritization | Alignment | Other]

## Decision
[1-2 sentences: what was decided]

## Context
[What prompted this]

## Alternatives Considered
[If discussed in transcript, otherwise omit]

Exec updates → memory/exec-updates/YYYY-MM-DD.md

# Exec Update — YYYY-MM-DD

**Source:** continual-learning (transcript extraction)

## Summary
[Key points from the update]

Strategy shifts → memory/strategy-reviews/YYYY-MM-DD_topic.md

# Strategy: [topic]

**Date:** YYYY-MM-DD
**Source:** continual-learning (transcript extraction)

## What changed
[Description of the shift]

## Rationale
[Why, if discussed]

Feedback insights → memory/feedback/YYYY-MM-DD.md

# Feedback Insights — YYYY-MM-DD

**Source:** continual-learning (transcript extraction)

## Themes
[Themes identified]

Also write a log entry to memory/learning-log/YYYY-MM-DD.md:

# Continual Learning Run — YYYY-MM-DD

**Transcripts processed:** [count]
**Items extracted:** [count by category]

## Items written
- [category] → [path]: [1-line summary]

4. Update AGENTS.md

After writing to memory, update the Learned sections in AGENTS.md:

  • Learned User Preferences — recurring corrections, stated broad rules
  • Learned Workspace Facts — durable facts about workspace, tools, workflows

Rules:

  • Update matching bullets in place (don't duplicate)
  • Add only net-new bullets
  • Deduplicate semantically similar bullets
  • Max 12 bullets per section
  • Plain bullet points only — no evidence tags, no metadata

5. Write back index

Update .cursor/hooks/state/continual-learning-index.json:

  • Store latest mtimes for all processed files
  • Remove entries for files that no longer exist on disk

Inclusion bar

Keep an item only if all are true:

  • Actionable in future sessions
  • Stable across sessions
  • Repeated in multiple transcripts, or explicitly stated as a broad rule
  • Non-sensitive

Exclusions

Never store:

  • Secrets, tokens, credentials, private personal data
  • One-off task instructions
  • Transient details (branch names, commit hashes, temporary errors)

Incremental Index Format

{
  "version": 1,
  "transcripts": {
    "/abs/path/to/file.jsonl": {
      "mtimeMs": 1730000000000,
      "lastProcessedAt": "2026-02-18T12:00:00.000Z"
    }
  }
}

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.