What problem does it solve? Teams lose track of which document version is current, overwrite history with in-place edits, and apply inconsistent naming across files. This Skill enforces a single mandatory filename pattern and versioning discipline so every output file is unambiguous, superseded copies are preserved, and audit documents stay append-only. ## Core Features & Use Cases - Mandatory filename pattern: Every output file follows [PREFIX_][Description]_YYYY-MM-DD_vXX_[suffix].[ext], with date, version shortcode, and internal/external suffix rules. - Version increment logic: Distinguishes number bumps (fixes that supersede) from letter bumps (parallel iterations), and resolves ambiguous "bump the version" requests by asking the user. - Deprecation handling: Moves superseded files into a deprecated/ folder without renaming or deleting them, preserving history byte-identically. - Append-only vs version-up decision: Classifies documents as audit records (append-only, never edited) or live artifacts (versioned up), preventing amendment-stacked files. - Use Case: When saving a revised pipeline playbook, the Skill names it CLI-SM-DATS_Pipeline_Playbook_2026-03-22_v03_I.md, retires v02 to deprecated/ unchanged, and confirms the increment type. ## Quick Start Ask the assistant to name and save a new version of a document, for example by saying "version this file" or "bump the version on my playbook draft."
