batch-process

# Batch Content Processing Process multiple content requirements through the ContentForge pipeline as a **sequential, checkpointed queue** with priority-based scheduling and event-driven progress tracking. Each piece runs the full 10-phase pipeline (plus Step 0.5) with all 10 quality gates — batch mode changes the intake, not the standards. ## When to Use Use `/contentforge:batch-process` when: - You have 2+ content pieces to produce - You want hands-off production of a whole queue (each piece needs a pre-set title — batch runs are non-interactive) - You need priority scheduling (urgent pieces first) - You want per-piece progress visibility and resumability - You're running agency-scale production (10-50+ pieces) ## What This Command Does 1. **Intake Multiple Requirements** — Read from the brand's tracking backend: local JSON (default), Google Sheets, Airtable, or a CSV file 2. **Build Execution Queue** — Validate rows and sort by priority 3. **Sequential Orchestration** — Run one full ContentForge pipeline per piece, in queue order; every phase of every piece is checkpointed, so an interrupted batch resumes where it stopped 4. **Progress Tracking** — Status table redrawn after each piece/phase event (piece started, gate passed, piece finished) 5. **Error Handling** — Automatic retry for transient failures (resuming from checkpoints), human escalation for persistent issues 6. **Completion Report** — Summary of all pieces: APPROVED, review_required, failed, with quality s...