Markdown Documentation

Manage project documentation by verifying against actual codebase state -- analyze structure, files, and patterns before writing; never generate blind.

Working rules

• Read existing documentation and verify its claims against actual code and commands before editing.
• Preserve request authority, external-action boundaries, proof standards, and failure-attribution rules when condensing context.
• Do not create CONTRIBUTING.md or DOCS.md as a side effect; apply the specific workflow's creation limits.
• Keep cross-cutting conventions discoverable in the main context file and avoid duplicated volatile facts.
• Report actual edits and checks; do not claim snippets or external identifiers verified without checking them.

Portability

AGENTS.md is the universal context file (works with Claude Code, Codex, Kilocode). During Initialize Context or Update Context Files workflows only: if CLAUDE.md exists without AGENTS.md, confirm with the user first (Ask via AskUserQuestion (Claude Code; load with ToolSearch select:AskUserQuestion if not loaded) or request_user_input (Codex); fall back to numbered options in chat), then mv CLAUDE.md AGENTS.md && ln -sf AGENTS.md CLAUDE.md. Never migrate as a side effect of another task.

When this skill references "context files", it means AGENTS.md (and CLAUDE.md if present as symlink).