How do I install the Batch Content Sprint Os skill?

Run npx skillmds@latest add dvcrn/batch-content-sprint-os in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Batch Content Sprint Os safe to use?

This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. Capability flags: docs only. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Batch Content Sprint Os?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Batch Content Sprint Os free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Batch Content Sprint Os?

dvcrn (@dvcrn) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Batch Content Sprint Os by dvcrn — Agent Skill

Name: Batch Content Sprint Os
Rating: 4.666666666666667 (3 reviews)
Author: dvcrn

Batch Content Sprint Os

Plan 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.

dvcrn Updated Sep 8, 2026 32 repo stars

File contents

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

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.

---name: batch-content-sprint-osdescription: Plan 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.---# 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 doesConvert content chaos into a realistic weekly sprint with delivery and recovery built in.## Workflow### 1) Define constraintsCapture:- available hours this week- team roles- output target- priority campaigns### 2) Build backlogClassify tasks:- must ship- should ship- nice to have### 3) Capacity and overcommit checkEstimate 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 executionCreate day-by-day blocks for:- ideation- scripting- recording- editing- publishing + repurposing### 5) Add anti-burnout guardrailsSet:- max deep-work hours/day- revision buffers- at least one low-load day- fallback content options### 6) Output sprint boardReturn:- 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.## LicenseCopyright (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 derivativesunder the same license.Commercial use requires a separate paid commercial license from **Razestar**.No trademark rights are granted.

Frequently asked questions