---
name: legal-discovery-tracking
description: "Excel tracker schema for Interrogatories/RFPs/RFAs — deterministic row-per-question tracking, Georgia discovery-cap counting rules, party-folder structure, and a 7-category strategy-document taxonomy; ships with a downloadable Georgia statutes-and-guide reference package. Use when a person asks to install or apply \"Legal Discovery Tracking\" (FTR-37) in a project, or when working in a project that has it installed."
---

# Legal Discovery Tracking (FTR-37, version 1.0)

> Generated from library record FTR-37 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

Excel tracker schema for Interrogatories/RFPs/RFAs — deterministic row-per-question tracking, Georgia discovery-cap counting rules, party-folder structure, and a 7-category strategy-document taxonomy; ships with a downloadable Georgia statutes-and-guide reference package

## When to use this skill

- A person asks to install, apply or update "Legal Discovery Tracking" (FTR-37) in a project.
- A project's agent instructions list legal-discovery-tracking as installed and the task touches what it covers.
- Requires first: FTR-36 (skill excel-tracker-base-capability).

## 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 FTR-36 (Excel Tracker Base Capability) is installed — this feature nests under it, not beside it, per FTR-36's own merge-behavior rule.
- Confirm the jurisdiction. This feature's schema, counting rules, and statutory citations are Georgia-specific (O.C.G.A. and Uniform Superior Court Rules) — a different jurisdiction's civil procedure code must be checked independently before assuming any of this transfers.

### Ask, only if needed
- If the project's Document ID / file-naming convention for discovery rounds isn't already established: ask what round-naming pattern to use (e.g., `DISC-01`, `Round-01`) rather than inventing one.
- If it's not clear whether the project's discovery rounds predate cluster-based strategy organization: ask before leaving `Strategy Group` blank on existing rows — don't assume.

### Write

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

### Confirm
Confirm: Legal Discovery Tracking is installed, nested under FTR-36's EXCEL TRACKER section — schema, nomenclature, folder structure, and strategy taxonomy are in place, and the Georgia_Discovery_Process_-_Statutes_and_Guide reference package is unzipped into the project's research location and pointed to from Agent Instructions. Want to install another, or is that everything for now?
## Other sections in the specification

- What this doesn't cover

These are in references/spec.md.

## Files in this skill

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