ruan-grobler

Campaign Brief Agent — Communication skill for Claude Code

Communication community

Claude agents turn a campaign brief into a checked cross-team launch plan, with validated MCP tools, an adversarial checker, human approval by exception and a dry-run Asana and Slack outbox.

How to install Campaign Brief Agent

This entry records only its repository, not the path inside it, so there is no exact command to give. Open ruan-grobler/campaign-brief-agent and copy the folder into ~/.claude/skills/, or the file into ~/.claude/agents/.

What Campaign Brief Agent does

Claude agents turn a campaign brief into a checked cross-team launch plan, with validated MCP tools, an adversarial checker, human approval by exception and a dry-run Asana and Slack outbox. Offline demo, no API key.

Alternatives in Communication

  • Gtm Strategy — Create GTM strategy with channels, messaging, and launch timeline 7.8k ★
  • Social Media Agent — 📲 An agent for sourcing, curating, and scheduling social media posts with human-in-the-loop 2.8k ★
  • Claude Skill Social Post — A Claude Code skill by Hao (駱君昊) that learns your Facebook voice and auto-posts to FB / IG / Threads / X with 625 ★

README

Campaign Brief Agent

[![License: MIT](https://img.shields.io/badge/license-MIT-blue.svg)](LICENSE) ![Node 22.18+](https://img.shields.io/badge/node-22.18%2B-339933?logo=node.js&logoColor=white) ![TypeScript strict](https://img.shields.io/badge/TypeScript-strict-3178C6?logo=typescript&logoColor=white) ![Tests: 38 passing](https://img.shields.io/badge/tests-38%20passing-brightgreen)

A team of Claude agents turns a marketing campaign brief into a checked, cross-team launch plan, then waits for a person before anything is sent.

All data is synthetic: the briefs, the client names, the team directory and the playbooks.

The business problem

A digital marketing agency gets a campaign brief as a document. Before any work starts, someone has to turn it into a plan that five teams can run: Media, PR, Creative, Organic and Data. Who does what, by when, what each team needs from the others, and what the client has left open.

That is slow coordination work, and the mistakes are expensive. A requirement buried on line 50 never gets planned. A deadline lands on a public holiday. A handoff is due after the team that needs it has started. A date the client marked "TBC" quietly becomes a commitment.

Before, after and the number

**Before.** The brief arrives as a document. A person reads it, splits it across five teams, works out dates around weekends, closed days and approval windows, chases what is missing, and then types it all into Asana and Slack.

**After.** The agents turn the brief into a plan the teams can run. Every task has an owner, a due date on a working day, at least two acceptance criteria and a confidence score. A separate checker traces every requirement in the brief to tasks, one revision fixes what it finds, and a pers