ia-md-docs

Manages project documentation: CLAUDE.md, AGENTS.md, README.md, CONTRIBUTING.md, DOCS.md. Use when asked to update, create, or init these context files. Not for general markdown editing.

Ilia Alshanetsky@iliaal

Install

openclaw skills install @iliaal/compound-eng-md-docs

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

Monorepos

Multi-package repo? Read monorepo.md before any update-*/init-* sweep (discovery commands, per-file scoping, context-loading rules). Enumerate targets; if the sweep would create or rewrite more than 3 files, stop: list planned targets and confirm before writing (same ask mechanism as in Portability above).

Arguments

Treat these as user-request modifiers: apply when the request contains the flag or equivalent phrasing. All workflows support:

--dry-run: preview changes as a diff, write nothing
--preserve: keep existing structure, fix inaccuracies only
--minimal: quick pass, high-level structure only
--thorough: deep analysis of all files

Backup Handling

Before overwriting: cp FILE FILE.backup; never auto-delete backups.

Report Format

After every operation, display a summary:

text

[OK] Updated AGENTS.md
  - Fixed build command
  - Added new directory to structure

[OK] Updated README.md
  - Added installation section
  - Updated badges

[--] CONTRIBUTING.md not found (skipped)

Verify

Every factual claim in updated docs verified against current codebase
No stale file paths or component names
Formatting renders correctly in markdown preview

Task-specific references

Read the relevant reference before implementing or reviewing the matching behavior:

For updating or initializing a context file, README, CONTRIBUTING, or API documentation: documentation-workflows.md.
For selecting durable context, organizing documentation, or editing prose: context-content-and-writing.md.

Existing specialized references, when the corresponding topic applies: