---
name: file-naming-and-versioning
description: "Naming format, multi-track document IDs, dual versioning, roll-up pattern. Use when a person asks to install or apply \"File Naming, Track IDs & Versioning\" (FTR-08) in a project, or when working in a project that has it installed."
---

# File Naming, Track IDs & Versioning (FTR-08, version 1.0)

> Generated from library record FTR-08 version 1.0, publish 20261102a. Review status: unreviewed. The complete specification is in references/spec.md and is the authority; this file is the operating procedure drawn from it.

## What this does

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

## When to use this skill

- A person asks to install, apply or update "File Naming, Track IDs & Versioning" (FTR-08) in a project.
- A project's agent instructions list file-naming-and-versioning as installed and the task touches what it covers.
- Requires first: FTR-04 (skill agent-role-and-project-identity).
- Required by: FTR-38 (skill multi-sub-project-awareness).

## Install procedure

Steps run in order. Assess comes first, every question in the Ask step is answered by the person before anything is written, and every write merges additively into the existing project files (read the file first, update an existing section in place, never overwrite).

### Assess first
- Confirm the project code is established (from Agent Role & Project Identity). Naming depends on it.
- Read `admin\AGENT_INSTRUCTIONS.md` for any existing track table or naming convention and carry it forward.
- Look at existing filenames in the project to see whether a track ID scheme is already in use.

### Ask, only if needed
- If the project has (or will have) 10+ documents and no track table exists: "Let's set up document tracks — functional groupings like Technical, Legal, Financial, Operations. I'll suggest a set based on your project type; you confirm." Use the project-type track defaults; confirm the finalized table.
- For legal projects, use the Legal file-naming convention from the Legal Preferences feature instead of the default format.
- Otherwise nothing to ask.

### Write

The full Write payload is in references/write-payload.md. It is applied exactly as written, with the merge rule above.

### 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?

## Files in this skill

- references/spec.md: the complete specification, unabridged.
- references/write-payload.md: the Write step on its own.