Claude Code Manual in Vault

Decisions

Pending: Manual structure — single file or multi-file?
Pending: Use Fetch MCP server for scraping docs?

User Tasks

Summary

Add the Claude Code documentation to the vault and keep it up to date.

Problem / Motivation

Claude Code evolves fast and has extensive documentation on tools, hooks, agents, skills, settings, and more. There’s no local reference in the vault — knowledge is scattered across web docs and session memory. Having it in vault/00_system/ makes it searchable, readable in Obsidian, and available as context for Claude itself.

Proposed Solution

Create an initial Claude Code manual at vault/00_system/external/claude-code-manual.md by pulling from official docs.
Set up a periodic update process to keep it current.

Placed in external/ since it documents an external tool, not Opus itself.

Open Questions

No open questions.

Phase Overview

Phase	Description	Status
Phase 1	Initial manual creation	—
Phase 2	Manual updates	—
Phase 3	Semi-automated updates	—

Phase 1: Initial Manual —

Goal: Create a comprehensive Claude Code manual from official documentation.

File / Feature	Details	Owner	Status
Research current docs	Gather all Claude Code documentation (tools, hooks, agents, skills, settings, MCP, etc.)	opus	—
Define sections	Tools, hooks, agents, skills, settings, MCP servers, keybindings, permissions, CLI flags	opus	—
Write manual	Create `vault/00_system/external/claude-code-manual.md` with structured sections	opus	—

Phase 2: Manual Updates —

Goal: Establish a periodic review process for the manual.

File / Feature	Details	Owner	Status
Update checklist	Define what sections to track and review process	mv	—
Periodic review	Manual check against Claude Code release notes	mv	—

Phase 3: Semi-Automated Updates —

Goal: Script-assisted updates with human review.

File / Feature	Details	Owner	Status
Update script	Script that checks Claude Code docs/changelog for changes	opus	—
Diff highlights	Show what changed since last update	opus	—
Human review	User approves changes before applying	mv	—

Prerequisites / Gap Analysis

Requirements

Requirement	Description
REQ-1	Access to Claude Code official documentation

Current State

Component	Status	Details
`vault/00_system/external/`	done	Directory exists
Claude Code manual	—	Not yet created

Gap (What’s missing?)

Gap	Effort	Blocker?
Initial manual content	Med	No
Update process definition	Low	No

Test

Manual tests

Test	Expected	Actual	Last
Manual exists at expected path	File at `vault/00_system/external/claude-code-manual.md`	pending	-
Manual covers all major features	Sections for tools, hooks, agents, skills, settings	pending	-
Update process takes < 5 minutes	Quick review cycle	pending	-

AI-verified tests

Scenario	Expected behavior	Verification method
…	…	…

E2E tests

Scenario	Assertion
…	…

Integration tests

Component	Coverage
…	…

Unit tests

Component	Tests	Coverage
…	…	…

History

Date	Event	Details
2026-02-26	Created	From brain dump
2026-02-27	Renumbered	From FR-037 to FR-033
2026-02-27	Expanded	Added Phase 1 for initial manual creation, renamed to reflect full scope
2026-02-28	Reformatted	Aligned to feature-request template

References

FR-048 (System Self-Review) — manual is the knowledge, self-review is the action
Fetch MCP server — potential tool for scraping docs

Opus Vault

Explorer