SOTEKProject AssistantPart ofsotekzone.com
Library / Organization

File Naming, Track IDs & Versioning

FTR-08version 1.0coreskill: file-naming-and-versioningskill review: unreviewed

In plain words

A consistent way to name and number your files so every document can be pointed to without confusion: one standard file name format, short document ID numbers grouped by topic, a version number on the file name and another inside the document, and a method for rolling several documents up into one summary.

Use it once a project will have more than a handful of documents. Instead of 'the March letter, second draft', you get a clear ID, and you stop hunting for which copy is current.

Technical summary

Naming format, multi-track document IDs, dual versioning, roll-up pattern

Install it

Download the skill folder (SKILL.md, with the full spec in references/spec.md), or the zip: file-naming-and-versioning-1.0.zip (4894 bytes, sha256 f7c2e9837dd692b6…).

Install first: FTR-04 Agent Role & Project Identity.

Needed by: FTR-38 Multi-Sub-Project Awareness.

Read it

For an AI without skills, hand over this line, or the plain markdown at id/FTR-08.md.

Fetch https://claude.sotekzone.com/v/20261102a/id/FTR-08.md and walk me through installing it.

File Naming, Track IDs & Versioning

Depends on: FTR-04 — Agent Role & Project Identity

What this is

The naming and versioning discipline for the whole project: the default filename format, the multi-track document ID system (for projects with 10+ documents), dual versioning (file version vs. internal footer version), and the roll-up/aggregate document pattern. This is what makes every document uniquely referenceable by a short code.

Assess first

Ask, only if needed

Write

Add this section to admin\AGENT_INSTRUCTIONS.md:

◆ FILE NAMING & VERSIONING

Track document format:
  [ProjectCode]-[TRACK][NUMBER]_[Short_Title].[ext]
General document format:
  [ProjectCode]_[DocType]_[Subject]_[YYYY-MM-DD]_v[X.X][_Draft].[ext]
Tracker files: static filename — version lives inside the file header,
  never in the name.

DOCUMENT ID SYSTEM (multi-track library, recommended for 10+ documents)
Every document gets a unique, short, referenceable ID.
Examples:
  THZ-T02_Network_Architecture.docx        (Technical, doc #2)
  THZ-L05_Door_Egress_Compliance_v5.docx   (Legal, doc #5, major rev)
  WOW-B01_Organization_Profile.docx        (Business, doc #1)

Track table (finalize at setup):
| Track | Code            | Scope                          | Folder            |
|-------|-----------------|--------------------------------|-------------------|
| [Name]| [Code]-[L]##    | [Scope]                        | docs\[folder]\    |
| Ref   | —               | Strategic docs w/o track IDs   | docs\reference\   |

Common track letters: T Technical · C Construction · P Procurement ·
F Financial · O Operations · L Legal · B Business · R Relations ·
M Marketing. Assign the next sequential number within a track when a new
document is created. Reference documents by their ID code in conversation.

DUAL VERSIONING
- File version: changes only when a major revision must be preserved as a
  distinct file on the file system (e.g., _v4 archived, _v5 current).
- Internal version: tracked in the document footer; increments freely
  without renaming the file (Draft v0.1 -> v0.2 -> v0.3 -> v1.0).
- Rule: rename the file only when the old version must be preserved
  separately. Otherwise update the footer version. Prevents filename churn.

VERSIONING RULES (summary)
- All files start at v1.0 or internal v0.1
- Draft files carry _Draft in the name; final files drop it
- Only current version in the active folder — previous to archive\ (never
  delete)
- One document = one tracker card = one active file

ROLL-UP / AGGREGATE PATTERN
When a master summary aggregates sub-documents:
- Always build sub-documents first; build the master/roll-up last
- The master reflects the current state of all sub-documents
- Never edit line-item detail in the master — edit the sub-document, then
  rebuild the roll-up

Confirm

Confirm: your naming convention, track ID system, and dual versioning are in the agent instructions — every document now gets a unique, referenceable code. Want to install another, or is that everything for now?