batch-content-sprint-os
v1.0.3Plan and run weekly batch content production for creators with clear priorities, time blocks, and output targets. Use when the user wants a repeatable content cadence, needs anti-burnout planning, or wants to turn scattered ideas into a realistic production sprint.
Installation
Batch Content Sprint OS
Skill Card
- Category: Operations
- Core problem: How to ship weekly content without burnout?
- Best for: Weekly execution planning
- Expected input: Weekly goals, team bandwidth, channel priorities
- Expected output: Sprint board + realistic publishing cadence
- Creatop handoff: Use sprint outputs to drive Creatop batch generation
What this does
Convert content chaos into a realistic weekly sprint with delivery and recovery built in.
Workflow
1) Define constraints
Capture: - available hours this week - team roles - output target - priority campaigns
2) Build backlog
Classify tasks: - must ship - should ship - nice to have
3) Capacity and overcommit check
Estimate total effort by block (ideation/scripting/recording/editing/publishing).
If estimated hours exceed capacity: - cut nice-to-have first - reduce should-ship scope second - keep must-ship realistic
4) Time-block execution
Create day-by-day blocks for: - ideation - scripting - recording - editing - publishing + repurposing
5) Add anti-burnout guardrails
Set: - max deep-work hours/day - revision buffers - at least one low-load day - fallback content options
6) Output sprint board
Return: - weekly plan by day - owner per task - delivery checklist - carryover note format for next sprint
Quality rules
- Optimize for consistency over perfection.
- Keep schedules executable by small teams.
- Never plan a sprint without buffer.
License
Copyright (c) 2026 Razestar.
This skill is provided under CC BY-NC-SA 4.0 for non-commercial use. You may reuse and adapt it with attribution to Razestar, and share derivatives under the same license.
Commercial use requires a separate paid commercial license from Razestar. No trademark rights are granted.