context-keeper

Record and restore project context across sessions using four persistent markdown registers.

1|Updated Apr 2, 2026

Search Tags:#planning #context #decision #governance #risk #register

Ready to run

npx skills add https://github.com/AnjinMeili/Claude-ITIL-Planner --skill context-keeper-anjinmeili

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: context-keeper
Source: https://github.com/AnjinMeili/Claude-ITIL-Planner/tree/main/planitil/skills/context-keeper
Command: npx skills add https://github.com/AnjinMeili/Claude-ITIL-Planner --skill context-keeper-anjinmeili

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Maintains four living registers that survive session resets: DECISIONS.md, ASSUMPTIONS.md, RISKS.md, and DEBT.md, ensuring critical project context is never lost.

Core Features & Use Cases

Keeps four persistent registers at project root for decisions, assumptions, risks, and debt
Append-only entries with date, rationale, and status to preserve history
Supports session continuity by restoring context from registers after reset and enabling governance traceability

Quick Start

Record a new entry by calling context-keeper to append a properly formatted item to the appropriate register.

Frequently Asked Questions about context-keeper

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

FAQPage Schema

How do I preserve project context across sessions after a reset?▼

To preserve project context across sessions, maintain persistent governance registers like DECISIONS.md and RISKS.md at your project root. This ensures critical decisions and assumptions survive session resets and enable fast resumption.

What is the best way to track project decisions and risks in markdown files?▼

Tracking project decisions and risks in markdown files requires appending entries with dates, rationale, and status fields to dedicated registers. This approach preserves governance traceability and maintains a clear history of project assumptions.

How do I maintain governance history when working with debt registers?▼

Maintaining governance history with debt registers involves enforcing append-only entries and cross-register linking. This preserves traceability by connecting related items across DEBT.md, DECISIONS.md, ASSUMPTIONS.md, and RISKS.md.

Can I restore project context from markdown registers after losing my session?▼

Yes, you can restore project context from markdown registers after losing a session. By reading the persistent DECISIONS.md, ASSUMPTIONS.md, RISKS.md, and DEBT.md files, you can quickly resume work with full governance traceability.

Does tracking project assumptions require any special frameworks or dependencies?▼

Tracking project assumptions does not require special frameworks or dependencies. It applies to any project using standard markdown files at the root directory to capture governance artifacts without external tools.

Why does append-only entry matter for project risk registers?▼

Append-only entry matters for project risk registers because it prevents the loss of historical context. Preserving the original entry alongside status updates ensures complete traceability and an accurate governance history.