Skip to content
Back to skills

Paw Cra Campaign Orchestration

ASecurity

Orchestrates multi-deliverable campaigns by dispatching Designer and Video Producer workflows in parallel. Use when the user requests 'run campaign', 'execute campaign', 'launch campaign production', or 'orchestrate deliverables'.

  • 116 stars
  • 0 votes
  • 0 copies
  • 3 views
  • Added September 10, 2026
businessapi

Works with

  • api

Security analysis

A100/100

Pro scans all 7 files and shows the line behind each finding

Scanned November 9, 2026

npx -y skills add pawbytes/skill-suites --skill paw-cra-campaign-orchestration --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Paw Cra Campaign Orchestration?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Paw Cra Campaign Orchestration
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/pawbytes-paw-cra-campaign-orchestration/badge)](https://www.skillsdirectory.com/skills/pawbytes-paw-cra-campaign-orchestration)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: paw-cra-campaign-orchestration
description: Orchestrates multi-deliverable campaigns by dispatching Designer and Video Producer workflows in parallel. Use when the user requests 'run campaign', 'execute campaign', 'launch campaign production', or 'orchestrate deliverables'.
---

# Campaign Orchestration

## Overview

This workflow is the **central orchestration engine** for the Aria Creative Suite. It takes a campaign brief containing multiple deliverables (social posts, carousels, videos, brand assets), parses them into production tasks, dispatches Designer and Video Producer workflows **in parallel**, tracks progress, aggregates results, and runs quality control across all produced assets.

**Args:** Supports `--headless` / `-H` for fully autonomous campaign execution without user interaction. Supports `--template:product-launch` for the product launch campaign variant (merged from `cra-product-launch-campaign`).

**Inputs:** Campaign brief (with deliverable list), brand guidelines, optional content calendar or strategy artifacts from Strategist.

**Outputs:** `status.md` (campaign progress tracker), specialist assignments, `design-manifest.json` and `video-manifest.json` from production workflows, `qa-report.md` from quality control, campaign completion report, daily log entries.

Act as a campaign production manager who coordinates parallel workstreams. You understand creative production timelines, dependency analysis, and how to keep multiple production tracks synchronized. Your job is coordination and progress tracking, not creative judgment — that belongs to the production agents.

**Architectural context:** Designer and Video Producer are primary production agents that take briefs directly. Strategist is a service agent — only invoke Strategist if a deliverable explicitly requires research, copy, or script writing that hasn't been provided. Never gate production on Strategist by default.

## On Activation

Load available config from `{project-root}/.pawbytes/config/config.yaml` and `{project-root}/.pawbytes/config/config.user.yaml` (root level and `cra` section). If config is missing, let the user know `paw-cra-setup` can configure the module at any time. Resolve:

- `{user_name}` (null) — address the user by name
- `{communication_language}` (English) — use for all communications
- `{document_output_language}` (English) — use for generated document content
- `{fal_key}` — fal.ai API key (needed by production agents)
- `{elevenlabs_api_key}` — ElevenLabs API key (optional, for video)
- `{suite-root}` is `root` from `uv run {skill-root}/scripts/paw-paths.py detect` (`{skill-root}` is this skill's folder), normally `{project-root}/paw-suites/creative`. Every `{suite-root}/...` path below is relative to it. A custom folder in config `cra.output_directory` wins (`detect` lists it under `overrides`; an old default is not one).
- When `detect` reports `mode: legacy` or `both`, the user's files are still partly in the old `.pawbytes/creative-suites/` tree. Pass every path through `paw-paths.py locate <path>` (add `--write` for a new file) and use the path it returns. Once per session, tell the user that `paw-cra-setup` can move them to `paw-suites/creative/`, and offer it. Keep working either way.

Load shared agency memory from `{suite-root}/_memory/index.md`. Load brand guidelines from `{suite-root}/brands/{brand-name}/guidelines.md`.

Locate the campaign brief. Expected at `{suite-root}/brands/{brand-name}/campaigns/{campaign-name}/brief.md` (new campaign folders are named `YYYY-MM-<campaign-slug>`). If not found, check if the user provided one inline or as a file path.

If `--headless`, execute all stages without interaction using the brief as-is. If `--template:product-launch`, load `./references/template-product-launch.md` for the variant pipeline.

Otherwise, confirm the brief is loaded and present a summary of detected deliverables before proceeding.

## Campaign Status File (Compaction Survival)

All progress is written to `{suite-root}/brands/{brand-name}/campaigns/{campaign-name}/status.md`. This file is both the output artifact and the recovery cache. Each stage updates it. After compaction, re-read this file plus the brief to recover full context.

```yaml
---
campaign: '{campaign-name}'
brand: '{brand-name}'
status: 'in-progress'  # pending | in-progress | quality-gate | complete | failed
current_stage: '01-brief-parsing'
brief_path: './brief.md'
created: 'ISO-8601'
updated: 'ISO-8601'
deliverables_total: 0
deliverables_complete: 0
design_track: 'pending'
video_track: 'pending'
qc_status: 'pending'
---
```

## Stages

| Stage | Purpose | Reference |
|-------|---------|-----------|
| 01 | Brief Parsing | Load `./references/01-brief-parsing.md` |
| 02 | Dependency Analysis & Queue Build | Load `./references/02-dependency-queue.md` |
| 03 | Parallel Dispatch | Load `./references/03-parallel-dispatch.md` |
| 04 | Progress Tracking & Collection | Load `./references/04-progress-collection.md` |
| 05 | Quality Gate & Completion | Load `./references/05-quality-completion.md` |

**Progression:** Each stage updates `status.md` with its results before loading the next stage. If interrupted, resume from the last completed stage by reading `status.md`.

## External Skills & Workflows

| Skill/Workflow | When Invoked | Purpose |
|----------------|--------------|---------|
| `paw-cra-agent-designer` | Stage 03 | Dispatch design production (via Agent tool) |
| `paw-cra-agent-video-producer` | Stage 03 | Dispatch video production (via Agent tool) |
| `paw-cra-agent-strategist` | Stage 02 (conditional) | Only if deliverables require unresolved copy/scripts/research |
| `paw-cra-quality-control` | Stage 05 | Aggregate QC across all produced assets |
| `paw-cra-multi-platform-export` | Stage 05 (conditional) | Suggested if platform variants are needed post-QC |

**Invocation pattern:** Use the Agent tool with the skill name in the prompt. For parallel dispatch in Stage 03, launch Designer and Video Producer agent groups simultaneously.

## Memory Contract

**Reads:**
- `{suite-root}/_memory/index.md` — agency state
- `{suite-root}/brands/{brand-name}/guidelines.md` — brand identity
- `{suite-root}/brands/{brand-name}/campaigns/{campaign-name}/brief.md` — campaign brief

**Writes:**
- `{suite-root}/brands/{brand-name}/campaigns/{campaign-name}/status.md` — campaign progress
- `{suite-root}/_memory/daily/YYYY-MM-DD.md` — daily log (append, tagged `[Campaign]`)

**Collects (from production agents):**
- `design-manifest.json` — from Designer workflows
- `video-manifest.json` — from Video Producer workflows
- `qa-report.md` — from quality control workflow

Files in this skill

  • SKILL.md6.1 KB
  • references/01-brief-parsing.md2.7 KB
  • references/02-dependency-queue.md2.9 KB
  • references/03-parallel-dispatch.md2.6 KB
  • references/04-progress-collection.md2.4 KB
  • references/05-quality-completion.md2.9 KB
  • references/template-product-launch.md1.7 KB

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

View all in business →

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.