documentation-management

name	documentation-management
description	Create, update, and audit durable project documentation. Use when code, setup, workflow, architecture, API behavior, or project structure must be reflected in docs.

Documentation Management

Use this skill when code, setup, workflows, or project structure changes need to be reflected in docs.

Workflow

1. Determine whether the task is init, update, or summarize.
2. Identify which docs are the source of truth in this repo.
3. Update existing docs before creating new ones. If the repo lacks docs and the task calls for durable documentation, create a minimal structure under docs/.
4. Keep file paths, commands, and examples accurate.
5. If external product, API, design, rollout, or synthesis context would improve the docs and the user enabled a relevant MCP, load the matching mcp-* skill first.
6. Cross-check plan artifacts if implementation changed the agreed approach.

Recommended Minimal Docs

Use these when initializing documentation or when the user asks for a fuller docs baseline:

• README.md
• docs/project-overview.md
• docs/codebase-summary.md
• docs/code-standards.md
• docs/system-architecture.md

Relevant MCP Skills

• mcp-context7 for exact external API or framework references
• mcp-github for issue, PR, release, or workflow details that docs should reflect
• mcp-figma for UI or design-system documentation inputs
• mcp-sentry for incident or release context that changes operational docs
• mcp-open-bridge for summarizing complex findings into durable docs

Output

Report:

• Docs created or updated
• Why they changed
• Any stale docs still needing work