Skip to content

tracker-sync

What it does

Scans your project folders, figures out which workflows are at which stage, uploads the latest .nbflow files to Google Drive, and updates a master Google Sheets tracker with everything — current version, status, fan-out state, links to files.

Without this, the master tracker drifts. With it, the tracker matches reality with one command.

When to use it

  • After shipping a workflow to V1 (approved + fanned out)
  • After a meaningful V0-N iteration during testing
  • After a variant lands (Lvl 1-4)
  • Weekly/end-of-day check-ins, to make sure the tracker hasn't drifted
  • Before a client meeting, so the tracker is current

Where it fits in the pipeline

flowchart LR
    A[Workflow ships<br/>or hits milestone] --> B[tracker-sync skill]
    B --> C[Scan project folders]
    C --> D[Upload .nbflow files<br/>to Drive]
    D --> E[Update Sheets tracker<br/>per tab]
    E --> F[Tracker matches reality]

How to invoke

sync the tracker

[scans projects/, uploads to Drive, updates the tracker tabs, reports what changed]

Trigger phrases:

  • "sync the tracker"
  • "update the tracker"
  • "run tracker-sync"

What you get back

A summary of changes made to the tracker:

  • Which workflows were added (new entries)
  • Which workflows had their version bumped
  • Which workflows had their status changed (testing → approved, etc.)
  • Which .nbflow files were uploaded to Drive
  • Direct links to the updated tracker tabs

What it touches

Target What it does
projects/{month}/{brand}/ folders Reads — never modifies
Google Drive Writes — uploads new .nbflow files and -generated.nbflow outputs
Google Sheets master tracker Writes — updates per-workflow rows
reference/version-registry.json Reads — uses this as the source of truth for current version

Example session

sync the tracker

Scanning projects/... Found 3 changes since last sync:

  • XYZG1: V0-5 → V1 (approved, fanned out to 4 accounts)
  • XYZS2: V0-2 → V0-3 (testing iteration — prompt fixes on Scene 03)
  • XYZG3: new workflow, V0-1

Uploading to Drive... - XYZG1-V1.nbflow → uploaded - XYZS2-V0-3.nbflow → uploaded - XYZG3-V0-1.nbflow → uploaded

Updating Sheets tracker... - "Approved Workflows" tab: 1 row added (XYZG1) - "Testing Workflows" tab: 1 row updated (XYZS2), 1 row added (XYZG3) - "Version History" tab: 3 rows appended

Tracker is now current. View it at [tracker URL].

Limitations

  • Needs Google service account credentials configured
  • One-way sync (project files → tracker). Doesn't import edits made directly in the Sheets back to the project files.
  • Doesn't archive old .nbflow versions in Drive — adds new ones, but cleanup is manual.
  • Doesn't sync -generated.nbflow files older than 30 days (to keep Drive lean)