skills.rest
georgernstgraf
georgernstgrafCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

knowledge-persistence

Persist session insights into docs/ai knowledge files at checkpoints.

Updated Apr 19, 2026
Search Tags:#architecture#decisions#persistence#handoff#knowledge#docs#session
One-click install
npx skills add https://github.com/georgernstgraf/aitranscribe-windows --skill knowledge-persistence-georgernstgraf
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: knowledge-persistence
Source: https://github.com/georgernstgraf/aitranscribe-windows/tree/main/skills/knowledge-persistence
Command: npx skills add https://github.com/georgernstgraf/aitranscribe-windows --skill knowledge-persistence-georgernstgraf

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Persist session context into the structured docs/ai knowledge files to create durable, searchable records of insights, decisions, and status changes.

Core Features & Use Cases

  • Persist accumulated understanding to docs/ai/HANDOFF.md, DECISIONS.md, ARCHITECTURE.md, CONVENTIONS.md, PITFALLS.md, DOMAIN.md, and STATE.md.
  • Create missing files and update existing ones at checkpoints during or after a productive session.
  • Use Case: Save the current session's insights at milestones for future reference and onboarding.

Quick Start

Persist new session insights into docs/ai seven files.

Frequently Asked Questions about knowledge-persistence

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I persist session knowledge into structured docs?▼

You persist session knowledge by applying checkpoints during or after a session to capture facts, decisions, patterns, and status changes into structured docs/ai knowledge files on disk.

What is the best way to save architecture decisions and handoff notes after a coding session?▼

Saving architecture decisions and handoff notes is done by persisting accumulated session understanding into dedicated files like ARCHITECTURE.md, DECISIONS.md, and HANDOFF.md.

How does knowledge persistence handle updates to existing architecture docs?▼

Knowledge persistence handles updates by reading existing files, writing new entries, and optionally rewriting ARCHITECTURE.md when structural changes occur during the session.

Can I create missing knowledge files like CONVENTIONS.md and PITFALLS.md during a session?▼

Yes, you can create missing knowledge files like CONVENTIONS.md, PITFALLS.md, DOMAIN.md, and STATE.md while updating existing ones at checkpoints during or after a productive session.

When do I need to persist session context into separate documentation files?▼

You need to persist session context into separate documentation files when you want to create durable, searchable records of insights, decisions, and status changes for future reference and onboarding.

Related Skills

Explore More Content & Communication Skills→
darelabs-techdarelabs-tech

dare-patterns

Mine brownfield software patterns via AST analysis to generate architectural documentation and JSON facts.

Official
Intermediate
whjelmarwhjelmar

Memory Search

Searches persistent memory markdown files for session summaries, decision records, and knowledge base entries.

Community
Intermediate
The13thNodeThe13thNode
3

document-release

Scan git diffs and update markdown documentation for releases.

Community
Intermediate
carson-sweetcarson-sweet
6

Session Export

Generate a portable markdown record of an AI session with transcripts and decision logs.

Community
Intermediate