What problem does it solve? Content teams need their tracking records and output files stored where collaboration actually happens, but moving between Google Sheets + Drive, Airtable, and local storage normally means manual credential setup, data re-entry, and risk of losing history. This Skill switches the active backend, verifies access, and optionally migrates existing records without deleting source data. ## Core Features & Use Cases - Backend Switching: Change the tracking.backend value in the brand profile between local, airtable, and google_sheets, taking effect immediately for the next content run. - Guided Credential Setup: Walks through Airtable personal access token creation or Google service account configuration, then verifies access by running the corresponding tracker script. - Additive Migration: Copies existing tracking records and output files to the new backend via backend-migrator.py, with idempotent dedup keyed on requirement_id and resumable re-runs. - Status Checks: The --status flag reports current backend health, record counts, and file locations. - Use Case: A team outgrows single-user local tracking and runs /contentforge:cf-switch-backend airtable to move 47 tracking records and 42 output files into a shared Airtable base while preserving the original local JSON. ## Quick Start Ask the assistant to switch the ContentForge tracking backend to Airtable and migrate existing records, or run it with --status to check which backend is currently active.
