deliverable-versioning

Every team eventually ends up with a folder full of report_FINAL.xlsx, report_FINAL_v2.xlsx, and report_FINAL_really.xlsx, and nobody trusts any of them. deliverable-versioning cures this with a set of mechanical rules: a file that has left your hands is never edited in place, new content becomes a new file; names use date and content, never the word final; one authoritative delivery directory per project is the source of truth, drafts live elsewhere; every send is logged in a ledger tracking date, filename, row count, and recipient, turning the question of what was actually sent into a one-second query instead of a chat-history archaeology dig.

The discipline is structural, not motivational. Before rebuilding a deliverable you check whether it already exists in the delivery directory. Superseded files stay in place but are marked in the ledger, and document references are updated to point at the current version. The entire system is a single SKILL file with zero dependencies. Legacy messy folders need one backlog sweep before the rules start paying off.

It is built for teams that routinely hand off datasets, reports, or proposals to clients, stakeholders, or partner teams. If a file has ever been edited after it was sent, or if nobody can say which version a decision was based on, this plugin is the fix.