Keep 의사 결정, 현재 작업 및 AI 세션의 다음 단계.

Context Docs는 읽을 수 있는 Markdown에 프로젝트 지식을 보존할 수 있도록 도와줍니다. AI 세션은 당신이 떠나는 곳을 선택할 수 있습니다. 당신의 코딩 대리인을 reusable 주기 무엇이 결정되고 왜곡되었는지 기록하기 위한 워크플로우, 무엇이 완료되거나 차단되고, 다음 것.

설치된 컨텍스트 관리 워크플로우 없이 사람들을 위해 설계, 사용 프로젝트의 기존 문서는 작은 설정과 수동 조직으로 가능한 한.

시작하다 · 보기 · 사용자 가이드 · 증거 · 기여

Status: 실험, 핵심 기술 v0.2.6 및 채택 기술 v0.1.15. v0.2.6 릴리스 노트 커버 메타 데이터 필터링, 휴대용 참고 및 자격이 된 합성 검사. 이전 후보자 unlinked-note 적용 간격은 남아 있습니다; 분리되는 설치된 체크 이름 주 견적 요청 결과 및 자격 보기. 출판 및 설치는 별도의 작업입니다. 이전 버전의 출시 내역 보기 버전, 기능 경계 및 유지 된 증거. Codex 및 Claude Code · Plain Markdown · MIT 라이센스

당신이 얻는 무엇

문서를 저장하기 전에 문서 시스템을 발명하지 않아야합니다. 일.

Context Docs

Keep decisions, current work and next steps across AI sessions.

Context Docs helps you preserve project knowledge in readable Markdown so a new AI session can pick up where you left off. Give your coding agent a reusable workflow for recording what was decided and why, what is done or blocked, and what to do next.

Designed for people without an established context-management workflow, it uses your project’s existing documents with as little setup and manual organization as possible.

Get started · See an example · User guide · Evidence · Contribute

Status: experimental, core skill v0.2.6 and adoption skill v0.1.15. The v0.2.6 release notes cover metadata filtering, portable references and qualified synthetic checks. The earlier candidate’s unlinked-note coverage gap remains; the separate installed check names the note explicitly. See results and qualifications. Publication and installation are separate actions. See release history for earlier versions, feature boundaries and retained evidence. For Codex and Claude Code · Plain Markdown · MIT licensed

What you get

You should not have to invent a documentation system before you can preserve your work. Context Docs gives your agent instructions to:

• Save what matters: decisions and their reasons, current work, blockers and next steps.
• Keep it useful: update stale sections, consolidate repetition and distinguish facts from proposals.
• Fit your project: use existing documents and choose content for their audience.
• Help the next session start: make the context discoverable from the README or documentation index.
• See progress in Markdown: show the documented goal, meaningful advances, blockers and next action in an existing section or a linked Markdown view.

For example, after working on an export feature, your project context might contain:

## Current work
CSV export is implemented; empty-input behavior still needs testing.

## Decision (maintainer-approved)
Keep the existing export API to preserve compatibility.

## Next step
Test empty input before calling the feature complete.

Illustrative content, not a required template. The agent should derive entries from your actual work and evidence. You review the changes; the next session reads the saved context. See a fuller before-and-after example.

For a runnable project, see the Reading Queue worked example: a small Cloudflare app, a real feature change and step-by-step prompts.

Get started