creative-batch-planning

---
name: creative-batch-planning
description: Use when the task is to plan batch size, variation axes, review gates, and fallback choices.
license: Apache-2.0
---

# Creative Batch Planning

## Outcome

Plan batch size, variation axes, review gates, and fallback choices. The result must be traceable to supplied inputs and pass the checks below.

## Inputs and prerequisites

- Creative brief, reviewers, budget, deadlines, delivery matrix, source assets, and final acceptance bar.
- Agentic Skill Garage local CLI, a shared project manifest, the chosen DCC/editor, and a human approval record.
- Confirm the target application's version and the actual capabilities available in this environment.

## Procedure

1. Turn the request into named outputs, audience, constraints, review owners, and stop conditions.
2. Choose a baseline and a small set of controlled variants; do not change every variable at once.
3. Schedule expensive generation or rendering only after pricing, resource, and approval checks.
4. Collect review notes as specific observable defects and map each to a corrective action.
5. Freeze the approved baseline and generate derivatives from that source, not from untracked copies.
6. Build a delivery manifest and independently verify every file, checksum, right, and required format.

## Quality gates

- No unapproved spend, publish, disclosure, or external upload.
- Stop when the agreed quality bar is met or the iteration cap is reached.
- The handoff lists unresolved defects and untested destinations instead of hiding them.

## Deliverable

An approved source baseline, output package, cost/decision record, and concise final handoff. Include the exact commands or application operations used, the files changed, and the checks that were actually run.

## Boundaries

- Keep source files unchanged; write new versions to an explicit output path.
- Do not transmit private assets or prompts to an external provider unless the user has explicitly approved that destination.
- Do not run paid generation or destructive application operations without clear authorization and a stated budget or scope.
- If a required application, plugin, model, or entitlement is absent, report the limitation and stop at the last verified stage.
- Separate measured results from visual judgment, assumptions, and recommendations.