knowledge-updater
Skill3 starsChanged 18 days agoMITView on GitHub
Update knowledge layer docs with automatic versioning. Use when updating strategy, segments, metrics, or competitive landscape. Snapshots the current state before overwriting so the retrospective agent can detect strategy drift.
1 other project uses a version of this, 1 of them edited.
Adopted by
Most recently taken up by
- ianklassen/ai-pm-systemedited, first seen Apr 12, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 1
- ianklassen/ai-pm-system★ 194% same
Wrote their own version · 0
None found.
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
- continual-learningSkill
- decision-loggerSkill
- eval-briefSkill
- exec-communicatorSkill
- experiment-designerSkill
- experiment-writeupSkill
- 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
11 rules. About 0 are common, 8 are distinctive, and 3 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈8
Distinctive · estimate
This author's own choices. Worth a look.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 8
Update knowledge layer documents (knowledge/) with automatic snapshotting.
- Distinctive: line 13
After quarterly planning when strategy shifts
- Distinctive: line 14
After significant market or competitive changes
- Distinctive: line 15
When asked "update my strategy", "refresh knowledge docs", or "knowledge update"
- Distinctive: line 21
Ask if not clear:
- Distinctive: line 28
Before making any changes, save the current version:
- Very specific: line 30
Create a timestamped snapshot directory: memory/knowledge-snapshots/YYYY-MM-DD/
- Very specific: line 32
Add a _changelog.md file to the snapshot:
- Distinctive: line 50
No orphaned references (e.g., removing a segment that's referenced elsewhere)
- Distinctive: line 54
If the knowledge update reflects a significant strategic shift, suggest logging it as a decision trace using the decision-logger skill.
- Distinctive: line 64
Decision coherence: Do knowledge updates align with decision traces?
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Knowledge Updater
Update knowledge layer documents (knowledge/) with automatic snapshotting. Before any update, the current version is saved to memory/knowledge-snapshots/ so the retrospective agent can track how strategy evolved over time.
When to Use
- Updating
knowledge/products/<product>/(brief, strategy, evals, metrics) or org files underknowledge/_template/ - After quarterly planning when strategy shifts
- After significant market or competitive changes
- When asked "update my strategy", "refresh knowledge docs", or "knowledge update"
Process
1. Identify What's Changing
Ask if not clear:
- Which knowledge doc(s) are being updated?
- What changed? (new strategy, updated segments, revised metrics, competitive shift)
- Why? (quarterly planning, market shift, exec direction, experiment results)
2. Snapshot Current State
Before making any changes, save the current version:
- Create a timestamped snapshot directory:
memory/knowledge-snapshots/YYYY-MM-DD/ - Copy the file(s) being updated into that directory with their original names
- Add a
_changelog.mdfile to the snapshot:
# Knowledge Snapshot — YYYY-MM-DD
**Reason for update:** [what triggered this change]
**Files updated:** [list]
## Changes Summary
- [File 1]: [what changed and why]
- [File 2]: [what changed and why]3. Make the Update
Edit the knowledge file(s) in knowledge/products/<product>/ (or the org template) with the new content. Ensure:
- Format matches the existing template structure
- Changes are clearly reflected in the content
- No orphaned references (e.g., removing a segment that's referenced elsewhere)
4. Log as a Decision (optional)
If the knowledge update reflects a significant strategic shift, suggest logging it as a decision trace using the decision-logger skill.
Output
- Updated knowledge file(s) in
knowledge/products/<product>/orknowledge/_template/ - Snapshot of previous version in
memory/knowledge-snapshots/YYYY-MM-DD/ - Changelog documenting what changed and why
Over time, snapshots enable:
- Drift detection: How has stated strategy evolved quarter over quarter?
- Decision coherence: Do knowledge updates align with decision traces?
- Retrospective analysis: The retrospective agent compares current knowledge to snapshots to surface gradual shifts
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.