What problem does it solve?
It solves the problem of keeping project documentation consistent and correctly scoped when behavior changes, so teams don’t lose durable history or create redundant, drifting records.
Core Features & Use Cases
- Artifact-selection protocol: Decide whether updates belong in the canonical document, a cumulative changelog, or a timestamped FIXES/CHANGES file based on change size and need.
- Documentation lifecycle governance: Ensure documentation is updated in the same change as the underlying behavior shift, and retire or consolidate duplicates when they accumulate.
- Format and traceability rules: Document impact clearly, include exact paths/commands/refs when it materially improves traceability, and keep documents scoped to one question.
- Validation-aware extensibility notes: When a feature variant is validated, document extensibility capability for future developers and link to evidence when major research was involved.
Quick Start
Use the documentation skill when you need to update README/changelog/docs and determine whether to write a canonical update, a cumulative entry, or a timestamped fixes-applied document for a specific change.