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
- thistleknot/skillstheir own version, first seen Nov 8, 2026
- docxology/templatetheir own version, first seen Nov 1, 2026
- JunfengRan/dev-envedited, first seen Oct 20, 2026
- ChatisTech/skillstheir own version, first seen Oct 11, 2026
- microsoft/agent-skillstheir own version, first seen Oct 8, 2026
- dhanji4U/skillstheir own version, first seen Oct 2, 2026
Other versions8 projects use a version of this.
Word for word · 0
None found.
Edited · 2
- ianklassen/ai-pm-system★ 195% same
- JunfengRan/dev-env★ 111% same
Wrote their own version · 6
- microsoft/agent-skills★ 3.2ksame name
- microsoft/skills★ 3.2ksame name
- docxology/template★ 23same name
- ChatisTech/skills★ 17same name
- dhanji4U/skills★ 2same name
- thistleknot/skills★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository24 other files it gives its agents.
- AGENTS.mdAGENTS.md
- docs/agents.mdAGENTS.md
- company-product-signalsSkill
- company-researcherSkill
- company-strategySkill
- pm-os-onboardingSkill
- brainstormingSkill
- decision-loggerSkill
- eval-briefSkill
- exec-communicatorSkill
- experiment-designerSkill
- experiment-writeupSkill
- knowledge-updaterSkill
- launch-postSkill
- launch-readinessSkill
- meeting-to-actionsSkill
- one-pagerSkill
- pptx-creatorSkill
- prd-writerSkill
- stakeholder-updateSkill
- strategy-connectorSkill
- what-ifSkill
- working-backwardsSkill
- writing-clearlySkill
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
- Distinctive: line 14
After a batch of important conversations (strategy sessions, PRD reviews, planning)
- Distinctive: line 121
After writing to memory, update the Learned sections in AGENTS.md:
- Distinctive: line 127
Update matching bullets in place (don't duplicate)
- Distinctive: line 128
Add only net-new bullets
- Distinctive: line 137
Remove entries for files that no longer exist on disk
- Distinctive: line 141
Keep an item only if all are true:
“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.
Files
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
- Read existing
AGENTS.md. - Load incremental index (if present).
- 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:
| Category | What to look for | Write to |
| Decision | User made or confirmed a product decision (PRD approval, scope change, launch/kill, prioritization shift, stakeholder alignment) | memory/decisions/ |
| Exec update | User drafted or discussed an executive status update, SLT summary, or program update | memory/exec-updates/ |
| Strategy shift | User discussed or changed strategic direction, pillars, positioning, or goals | memory/strategy-reviews/ |
| Feedback insight | User analyzed customer feedback, VOC themes, or support trends | memory/feedback/ |
| User preference | Recurring correction or stated broad rule about how the AI should behave | AGENTS.md → Learned User Preferences |
| Workspace fact | Durable fact about the workspace, tools, file paths, or workflows | AGENTS.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"
}
}
}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
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.

