Start here.
Keep what matters.

STEP 01

Install the skills.

You'll need Codex or Claude Code and a project folder you can edit. Start with one project you already work on. No cloud account or background service is needed for Context Docs itself.

Install context-docs, the maintenance workflow, and adopt-context-docs, its setup companion. Keep the complete folders side by side.

Use $skill-installer to install both skills from jaredchu/context-docs:
- skills/context-docs
- skills/adopt-context-docs
Install them together in ~/.agents/skills/.
Preserve existing installations and local customizations; report version
mismatches before upgrading.

git clone https://github.com/jaredchu/context-docs.git
cd context-docs
mkdir -p ~/.claude/skills
cp -r skills/context-docs skills/adopt-context-docs ~/.claude/skills/

STEP 02

Set up one project.

Open the project you want to maintain in your coding agent. If you used the clone commands above, use cd to enter your own project folder, then start a new Claude Code session there.

The agent inspects existing documentation, reuses a suitable context entry point or creates one, and adds or reuses a maintenance rule in project instructions. It should fit the project's layout, rather than move everything into a new structure.

Before you move on

• Find the context entry point: the starting document linked from the README or documentation index. Its actual path is also recorded in the adoption marker.
• Check that the maintenance rule is in instructions your agent actually loads. The Claude Code reference explains how to confirm this.
• Review what was written. Correct unsupported claims and keep private or machine-specific information out of shared docs.

You do not need to enable event logging to use this workflow. Existing logging settings are preserved; optional logging is explained in the reference guide.

STEP 03

Work, then save useful changes.

After work that changes a decision, the current state or the next step, ask:

Use context-docs to update this project's context from the work we just completed.

Review the changes in your agent or editor. Keep enough detail for the next reader to continue: what is known, why a decision was made, and what still needs doing. Replace stale facts and link to detailed evidence instead of pasting the entire conversation.

## 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.

This is an illustration, not a required template or an evaluation result. Your agent should use evidence from your project and preserve its useful existing structure.

STEP 04

Give the next session a starting point.

Open the same project in a new session and ask:

Read this project's context entry point and its relevant linked documents,
then continue with the next task.

If the agent cannot find the entry point, provide the path recorded during setup. Ask it to check relevant code or other evidence before relying on a claim that may be stale.

The saved document helps the agent get oriented. It does not automatically load every file or restore the previous conversation. You still decide what to work on next.