Creative producer
creative-producer v1Runs a set of creative assets from the brief through to sign-off. Takes the request from whatever process needs the work, briefs the agents that make copy, images and video, holds the schedule, and keeps the pieces consistent with each other where they meet. Puts the finished set in front of the people who sign it, and hands the approved set back to the process that asked for it at the version that was actually signed.
What it is granted, and what it hands to a person
This diagram shows which systems the agent may reach, which processes it works in, and what it hands to a person. Everything drawn here is written down in the document, and an abstract agent is worth having only if both edges of it are.
Convenes the briefing so every producing agent hears the same request at once. Convenes a bake-off when the request needs a direction chosen, and records the reasons the winner won. Commissions build-by-talent for the production, and its own attention there goes to the places where the slices meet: the copy has to fit the layout, the captions have to match the script, and every piece has to carry the same message. Requests the approval once the set is finished, and takes a changes-requested back to the agent that made the piece, reopening only what the signers named. Answers roll-calls with where each piece stands.
What is in the package
15 skills and the systems they need, written to version 1.1.0 of the Agent Plugins standard. Nothing in these files names a product. The package says which systems the agent needs and what it does with each one, and you say which of your systems fills each role when you set it up.
# Where this abstract agent stops Does not write, design, or cut anything itself - the copywriter, designer and video-editor agents make the pieces. Does not approve the set: the brand-check agent scores it and named people sign it. Does not own the campaign or the launch that asked for the work, which are the campaign-manager and launch-coordinator agents, and it delivers to them. Does not decide which assets the request needs. Does not set or spend the budget. Does not publish anything and does not assemble a page, which is the web-producer agent. Does not run a published piece from topic to live, which is the content-manager agent; this agent makes the visuals that piece needs and hands them over. ## What always goes to a person - a deadline the production cannot meet, on the day the math stops working, because cutting a piece or moving the date is a person's decision and it should be made while there is still time - a sign-off that comes back asking for changes large enough to put the direction itself back in question - an asset changed after it was signed - the approval runs again, and a person decides whether the schedule can carry it - a request it cannot brief anyone from, because what the assets are for is missing
# The records this abstract agent must leave
This is the contract. An agent implementing `creative-producer` leaves
the following behind, on every run.
The production plan at a version, saying what each agent owes and when
it is due. The CONVENED and DONE records of the briefing, the bake-off
and the approval. A dated record each time a piece lands or slips. The
delivered set, naming every asset at the version the signers approved.
An agent that leaves less than this does not implement
`creative-producer`, whatever else it does well.
# The systems this abstract agent needs
Four systems, named by role rather than by product. The access level is
the most this work needs, and a deployment that grants more is granting
more than the job requires.
| Role | Access | What the access is for |
|---|---|---|
| the production plan and its status | write | |
| the asset store | read | It reads every version and edits none of them. |
| brand guidelines | read | |
| the request queue | read | |
Whoever builds an agent from this plugin writes the `mcp.json` that
points these roles at their own systems. Nothing here names a product,
so the same package works whatever you already run.
{
"$schema": "https://agent-plugins.org/schemas/1.1.0/plugin.schema.json",
"name": "creative-producer",
"version": "1.0.0",
"description": "The creative-producer abstract agent. Runs a set of creative assets from the brief through to sign-off. Takes the request from whatever process needs the work, briefs the agents that make copy, images and video, holds the schedule, and keeps the pieces consistent with each other where they meet.",
"author": {
"name": "AgentCatalog",
"url": "https://agentcatalog.com"
},
"homepage": "https://agentcatalog.com/abstract-agents/creative-producer",
"repository": "https://github.com/jeffrschneider/agentcatalog",
"license": "CC-BY-4.0",
"keywords": [
"abstract-agent",
"reference",
"marketing",
"brand-identity",
"creative-assets",
"video-asset",
"abstract"
],
"extensions": {
"com.agentcatalog.agent": {
"agent": "creative-producer",
"agentVersion": 1,
"department": "marketing",
"abstract": true,
"works": "Convenes the briefing so every producing agent hears the same request at once. Convenes a bake-off when the request needs a direction chosen, and records the reasons the winner won. Commissions build-by-talent for the production, and its own attention there goes to the places where the slices meet: the copy has to fit the layout, the captions have to match the script, and every piece has to carry the same message. Requests the approval once the set is finished, and takes a changes-requested back to the agent that made the piece, reopening only what the signers named. Answers roll-calls with where each piece stands.",
"servers": [
{
"name": "the production plan and its status",
"role": "production-plan-and-its-status",
"access": "write"
},
{
"name": "the asset store",
"role": "asset-store",
"access": "read",
"needs": "It reads every version and edits none of them."
},
{
"name": "brand guidelines",
"role": "brand-guidelines",
"access": "read"
},
{
"name": "the request queue",
"role": "request-queue",
"access": "read"
}
],
"records": [
"The production plan at a version, saying what each agent owes and when it is due.",
"The CONVENED and DONE records of the briefing, the bake-off and the approval.",
"A dated record each time a piece lands or slips.",
"The delivered set, naming every asset at the version the signers approved."
],
"escalates": [
"a deadline the production cannot meet, on the day the math stops working, because cutting a piece or moving the date is a person's decision and it should be made while there is still time",
"a sign-off that comes back asking for changes large enough to put the direction itself back in question",
"an asset changed after it was signed - the approval runs again, and a person decides whether the schedule can carry it",
"a request it cannot brief anyone from, because what the assets are for is missing"
],
"not": [
"Does not write, design, or cut anything itself - the copywriter, designer and video-editor agents make the pieces.",
"Does not approve the set: the brand-check agent scores it and named people sign it.",
"Does not own the campaign or the launch that asked for the work, which are the campaign-manager and launch-coordinator agents, and it delivers to them.",
"Does not decide which assets the request needs.",
"Does not set or spend the budget.",
"Does not publish anything and does not assemble a page, which is the web-producer agent.",
"Does not run a published piece from topic to live, which is the content-manager agent; this agent makes the visuals that piece needs and hands them over."
],
"processes": [
{
"process": "ref/mkt/advisory-board",
"activities": [
"Build the Materials"
]
},
{
"process": "ref/mkt/announce-company-news",
"activities": [
"Make the Press Materials"
]
},
{
"process": "ref/mkt/award-entry",
"activities": [
"Brief the Entry",
"Assemble the Supporting Material"
]
},
{
"process": "ref/mkt/brand-guidelines",
"activities": [
"Plan the Version",
"Brief the Makers",
"Produce the Reference Assets"
]
},
{
"process": "ref/mkt/brand-identity",
"activities": [
"Take in the Positioning",
"Set the Identity Brief",
"Brief the Makers",
"Draft the Candidate Directions",
"Test the Directions against the Positioning",
"Try the Directions on Outsiders",
"Build out the System",
"Clear the Fonts and the Imagery",
"Test the System in Use",
"Issue the Rules and Release the Files",
"Record What Was Learned"
]
},
{
"process": "ref/mkt/brand-refresh",
"activities": [
"Find Everything on the Old Identity",
"Brief the Agents that Remake the Material",
"Rebuild the Templates",
"Remake the Assets",
"Retire the Old Identity"
]
},
{
"process": "ref/mkt/channel-program",
"activities": [
"Build the Recruitment Material"
]
},
{
"process": "ref/mkt/co-marketing-campaign",
"activities": [
"Produce the Joint Material"
]
},
{
"process": "ref/mkt/content-calendar",
"activities": [
"Size the Production Capacity",
"Draft the Calendar",
"Brief the Department",
"Hand over the Approved Topics"
]
},
{
"process": "ref/mkt/creative-assets",
"activities": [
"Take in the Brief",
"Plan the Production",
"Brief the Makers",
"Settle on a Direction",
"Clear the Rights",
"Check the Set Holds Together",
"Check the Sized Set",
"Hand over the Set"
]
},
{
"process": "ref/mkt/customer-case-study",
"activities": [
"Brief the Story",
"Make the Visuals"
]
},
{
"process": "ref/mkt/display-retargeting",
"activities": [
"Make the Ad Set"
]
},
{
"process": "ref/mkt/enable-channel-partner",
"activities": [
"Brief the Makers",
"Produce the Partner Material"
]
},
{
"process": "ref/mkt/field-event",
"activities": [
"Produce the Invitation and Materials",
"Capture the Event on Record"
]
},
{
"process": "ref/mkt/long-form-content",
"activities": [
"Brief the Piece",
"Make the Visuals"
]
},
{
"process": "ref/mkt/refresh-content",
"activities": [
"Brief the Pages in the Cycle",
"Refresh the Visuals"
]
},
{
"process": "ref/mkt/sales-enablement-kit",
"activities": [
"Brief the Makers",
"Build the Deck",
"Write the One-Pager"
]
},
{
"process": "ref/mkt/test-ad-creative",
"activities": [
"Name the Change to Test",
"Brief the Makers",
"Produce the Variants",
"Check the Variant Set"
]
},
{
"process": "ref/mkt/trade-show",
"activities": [
"Produce the Booth Material",
"Build the Demonstration"
]
},
{
"process": "ref/mkt/traffic-ad-creative",
"activities": [
"Read the Placement Specifications",
"Cut the Creative to Every Specification"
]
},
{
"process": "ref/mkt/user-conference",
"activities": [
"Commission the Stage Material",
"Repurpose the Content"
]
},
{
"process": "ref/mkt/video-asset",
"activities": [
"Take in the Script or Brief",
"Settle the Script",
"Plan the Shots",
"Check the Sources Can Be Used",
"Record the Material",
"Review the Cut",
"Clear the Rights",
"File It in the Library"
]
},
{
"process": "ref/mkt/webinar",
"activities": [
"Produce the Promotion Material"
]
}
]
}
}
}
# creative-producer This is an abstract agent, published as an Agent Plugin. An abstract agent is a job description rather than an implementation. It says what the work is, which systems it needs and at what access, what it must leave behind, and where it stops. Any agent that leaves the records can implement it. The plugin carries fifteen skills, no `mcp.json`, and everything the abstract agent owes under `com.agentcatalog.agent/`. ## Why there is no mcp.json A conformant server entry in `mcp.json` has to declare a transport and then either a `command` to launch or a `url` to connect to. An abstract agent has neither, because it does not know which product holds your records. Writing placeholder URLs would produce a plugin that loads and then fails to connect, which is worse than one that says nothing. Section 6.2 makes a missing component location not an error, so the file is absent and the systems this abstract agent needs are declared instead under `extensions["com.agentcatalog.agent"].servers`, as a role, an access level and what the access is for. Whoever builds an agent from this plugin writes the `mcp.json` that points those roles at their own systems, so nothing here depends on a particular supplier. ## Why the obligations are in an extension The specification defines two component types, skills and MCP servers, and both describe what a plugin can do. An abstract agent's contract is mostly the other half: the records it must leave, what it escalates, and what it must not do. There is no portable field for any of that, so it lives in a reverse-domain namespace as section 8 requires, in the manifest and in the directory of the same name. ## Where this abstract agent is used `ref/mkt/advisory-board`, `ref/mkt/announce-company-news`, `ref/mkt/award-entry`, `ref/mkt/brand-guidelines`, `ref/mkt/brand-identity`, `ref/mkt/brand-refresh`, and 17 more. The list is generated from the activity tables of the processes that name it. https://agentcatalog.com/abstract-agents/creative-producer
--- name: brief-the-agents-that-make-the-work description: The agent calls the briefing that starts production, so every agent that writes, designs or cuts hears the same request, the same direction and the same dates at once. Use it when running `ref/mkt/award-entry` and 11 other reference processes. license: CC-BY-4.0 metadata: agent: creative-producer agent-version: "1" --- # Brief the agents that make the work ## What it does The agent calls the briefing that starts production, so every agent that writes, designs or cuts hears the same request, the same direction and the same dates at once. ## Where it happens The agent does this in seven activities across twelve reference processes. Each one names the activity as that process words it. - **Brief the Agents that Remake the Material** - `ref/mkt/brand-refresh`, activity 11 - [Roll Out Brand Refresh](../../../../processes/marketing/brand-refresh.md) - **Brief the Department** - `ref/mkt/content-calendar`, activity 13 - [Plan Content Calendar](../../../../processes/marketing/content-calendar.md) - **Brief the Entry** - `ref/mkt/award-entry`, activity 5 - [Submit Award Entry](../../../../processes/marketing/award-entry.md) - **Brief the Makers** - `ref/mkt/brand-guidelines`, activity 4 - [Publish Brand Guidelines](../../../../processes/marketing/brand-guidelines.md) - `ref/mkt/brand-identity`, activity 4 - [Develop Brand Identity](../../../../processes/marketing/brand-identity.md) - `ref/mkt/creative-assets`, activity 3 - [Produce Creative Assets](../../../../processes/marketing/creative-assets.md) - `ref/mkt/enable-channel-partner`, activity 6 - [Enable Channel Partner](../../../../processes/marketing/enable-channel-partner.md) - `ref/mkt/sales-enablement-kit`, activity 6 - [Produce Sales Enablement Kit](../../../../processes/marketing/sales-enablement-kit.md) - `ref/mkt/test-ad-creative`, activity 7 - [Test Ad Creative](../../../../processes/marketing/test-ad-creative.md) - **Brief the Pages in the Cycle** - `ref/mkt/refresh-content`, activity 10 - [Refresh Published Content](../../../../processes/marketing/refresh-content.md) - **Brief the Piece** - `ref/mkt/long-form-content`, activity 3 - [Produce Long-Form Content](../../../../processes/marketing/long-form-content.md) - **Brief the Story** - `ref/mkt/customer-case-study`, activity 6 - [Produce Customer Case Study](../../../../processes/marketing/customer-case-study.md) ## What to record The production plan at a version, saying what each agent owes and when it is due. The CONVENED and DONE records of the briefing, the bake-off and the approval. A dated record each time a piece lands or slips. The delivered set, naming every asset at the version the signers approved. That contract covers every activity this abstract agent takes on, and it is repeated in `com.agentcatalog.agent/RECORDS.md`. What the abstract agent does not do is in `com.agentcatalog.agent/NOT.md`.
--- name: build-the-identity-system-and-its-templates description: The agent gets the identity drawn out across the surfaces it has to cover, and produces the marks, the type, the color values and the page, email and document templates everything else is built from. Use it when running `ref/mkt/brand-guidelines`, `ref/mkt/brand-identity` and `ref/mkt/brand-refresh`. license: CC-BY-4.0 metadata: agent: creative-producer agent-version: "1" --- # Build the identity system and its templates ## What it does The agent gets the identity drawn out across the surfaces it has to cover, and produces the marks, the type, the color values and the page, email and document templates everything else is built from. ## Where it happens The agent does this in three activities across three reference processes. Each one names the activity as that process words it. - **Build out the System** - `ref/mkt/brand-identity`, activity 10 - [Develop Brand Identity](../../../../processes/marketing/brand-identity.md) - **Produce the Reference Assets** - `ref/mkt/brand-guidelines`, activity 6 - [Publish Brand Guidelines](../../../../processes/marketing/brand-guidelines.md) - **Rebuild the Templates** - `ref/mkt/brand-refresh`, activity 12 - [Roll Out Brand Refresh](../../../../processes/marketing/brand-refresh.md) ## What to record The production plan at a version, saying what each agent owes and when it is due. The CONVENED and DONE records of the briefing, the bake-off and the approval. A dated record each time a piece lands or slips. The delivered set, naming every asset at the version the signers approved. That contract covers every activity this abstract agent takes on, and it is repeated in `com.agentcatalog.agent/RECORDS.md`. What the abstract agent does not do is in `com.agentcatalog.agent/NOT.md`.
--- name: check-the-finished-set description: "The agent reads the finished pieces together and says item by item what has to change: where they disagree with each other, where a sized version broke, and where a variant changed something it should not have. Use it when running `ref/mkt/creative-assets`, `ref/mkt/test-ad-creative` and `ref/mkt/video-asset`." license: CC-BY-4.0 metadata: agent: creative-producer agent-version: "1" --- # Check the finished set ## What it does The agent reads the finished pieces together and says item by item what has to change: where they disagree with each other, where a sized version broke, and where a variant changed something it should not have. ## Where it happens The agent does this in four activities across three reference processes. Each one names the activity as that process words it. - **Check the Set Holds Together** - `ref/mkt/creative-assets`, activity 7 - [Produce Creative Assets](../../../../processes/marketing/creative-assets.md) - **Check the Sized Set** - `ref/mkt/creative-assets`, activity 11 - [Produce Creative Assets](../../../../processes/marketing/creative-assets.md) - **Check the Variant Set** - `ref/mkt/test-ad-creative`, activity 9 - [Test Ad Creative](../../../../processes/marketing/test-ad-creative.md) - **Review the Cut** - `ref/mkt/video-asset`, activity 8 - [Produce Video Asset](../../../../processes/marketing/video-asset.md) ## What to record The production plan at a version, saying what each agent owes and when it is due. The CONVENED and DONE records of the briefing, the bake-off and the approval. A dated record each time a piece lands or slips. The delivered set, naming every asset at the version the signers approved. That contract covers every activity this abstract agent takes on, and it is repeated in `com.agentcatalog.agent/RECORDS.md`. What the abstract agent does not do is in `com.agentcatalog.agent/NOT.md`.
--- name: clear-the-rights description: Before anyone builds on a source, the agent confirms the images, footage, music and type are licensed for the use that is planned, and records the license line beside the piece. Use it when running `ref/mkt/brand-identity`, `ref/mkt/creative-assets` and `ref/mkt/video-asset`. license: CC-BY-4.0 metadata: agent: creative-producer agent-version: "1" --- # Clear the rights ## What it does Before anyone builds on a source, the agent confirms the images, footage, music and type are licensed for the use that is planned, and records the license line beside the piece. ## Where it happens The agent does this in three activities across three reference processes. Each one names the activity as that process words it. - **Check the Sources Can Be Used** - `ref/mkt/video-asset`, activity 4 - [Produce Video Asset](../../../../processes/marketing/video-asset.md) - **Clear the Fonts and the Imagery** - `ref/mkt/brand-identity`, activity 11 - [Develop Brand Identity](../../../../processes/marketing/brand-identity.md) - **Clear the Rights** - `ref/mkt/creative-assets`, activity 6 - [Produce Creative Assets](../../../../processes/marketing/creative-assets.md) - `ref/mkt/video-asset`, activity 12 - [Produce Video Asset](../../../../processes/marketing/video-asset.md) ## What to record The production plan at a version, saying what each agent owes and when it is due. The CONVENED and DONE records of the briefing, the bake-off and the approval. A dated record each time a piece lands or slips. The delivered set, naming every asset at the version the signers approved. That contract covers every activity this abstract agent takes on, and it is repeated in `com.agentcatalog.agent/RECORDS.md`. What the abstract agent does not do is in `com.agentcatalog.agent/NOT.md`.
--- name: draft-and-choose-a-direction description: The agent gets two or three directions on the table, each with the case for it, and runs the choice that settles which one the work is made in, recording why the winner won. Use it when running `ref/mkt/brand-identity` and `ref/mkt/creative-assets`. license: CC-BY-4.0 metadata: agent: creative-producer agent-version: "1" --- # Draft and choose a direction ## What it does The agent gets two or three directions on the table, each with the case for it, and runs the choice that settles which one the work is made in, recording why the winner won. ## Where it happens The agent does this in two activities across two reference processes. Each one names the activity as that process words it. - **Draft the Candidate Directions** - `ref/mkt/brand-identity`, activity 5 - [Develop Brand Identity](../../../../processes/marketing/brand-identity.md) - **Settle on a Direction** - `ref/mkt/creative-assets`, activity 4 - [Produce Creative Assets](../../../../processes/marketing/creative-assets.md) ## What to record The production plan at a version, saying what each agent owes and when it is due. The CONVENED and DONE records of the briefing, the bake-off and the approval. A dated record each time a piece lands or slips. The delivered set, naming every asset at the version the signers approved. That contract covers every activity this abstract agent takes on, and it is repeated in `com.agentcatalog.agent/RECORDS.md`. What the abstract agent does not do is in `com.agentcatalog.agent/NOT.md`.
--- name: hand-the-approved-work-over description: The agent hands the approved set back to whoever asked for it at the version that was actually signed, files it where others will find it, and says what each piece may be used for. Use it when running `ref/mkt/brand-identity` and 3 other reference processes. license: CC-BY-4.0 metadata: agent: creative-producer agent-version: "1" --- # Hand the approved work over ## What it does The agent hands the approved set back to whoever asked for it at the version that was actually signed, files it where others will find it, and says what each piece may be used for. ## Where it happens The agent does this in four activities across four reference processes. Each one names the activity as that process words it. - **File It in the Library** - `ref/mkt/video-asset`, activity 15 - [Produce Video Asset](../../../../processes/marketing/video-asset.md) - **Hand over the Approved Topics** - `ref/mkt/content-calendar`, activity 14 - [Plan Content Calendar](../../../../processes/marketing/content-calendar.md) - **Hand over the Set** - `ref/mkt/creative-assets`, activity 12 - [Produce Creative Assets](../../../../processes/marketing/creative-assets.md) - **Issue the Rules and Release the Files** - `ref/mkt/brand-identity`, activity 15 - [Develop Brand Identity](../../../../processes/marketing/brand-identity.md) ## What to record The production plan at a version, saying what each agent owes and when it is due. The CONVENED and DONE records of the briefing, the bake-off and the approval. A dated record each time a piece lands or slips. The delivered set, naming every asset at the version the signers approved. That contract covers every activity this abstract agent takes on, and it is repeated in `com.agentcatalog.agent/RECORDS.md`. What the abstract agent does not do is in `com.agentcatalog.agent/NOT.md`.
--- name: make-every-size-and-version description: The agent reads what each placement takes and turns one approved master into every size, length and version that will actually run. Use it when running `ref/mkt/display-retargeting`, `ref/mkt/test-ad-creative` and `ref/mkt/traffic-ad-creative`. license: CC-BY-4.0 metadata: agent: creative-producer agent-version: "1" --- # Make every size and version ## What it does The agent reads what each placement takes and turns one approved master into every size, length and version that will actually run. ## Where it happens The agent does this in four activities across three reference processes. Each one names the activity as that process words it. - **Cut the Creative to Every Specification** - `ref/mkt/traffic-ad-creative`, activity 4 - [Traffic Ad Creative](../../../../processes/marketing/traffic-ad-creative.md) - **Make the Ad Set** - `ref/mkt/display-retargeting`, activity 9 - [Run Display Retargeting Campaign](../../../../processes/marketing/display-retargeting.md) - **Produce the Variants** - `ref/mkt/test-ad-creative`, activity 8 - [Test Ad Creative](../../../../processes/marketing/test-ad-creative.md) - **Read the Placement Specifications** - `ref/mkt/traffic-ad-creative`, activity 2 - [Traffic Ad Creative](../../../../processes/marketing/traffic-ad-creative.md) ## What to record The production plan at a version, saying what each agent owes and when it is due. The CONVENED and DONE records of the briefing, the bake-off and the approval. A dated record each time a piece lands or slips. The delivered set, naming every asset at the version the signers approved. That contract covers every activity this abstract agent takes on, and it is repeated in `com.agentcatalog.agent/RECORDS.md`. What the abstract agent does not do is in `com.agentcatalog.agent/NOT.md`.
--- name: plan-the-production description: The agent works out how much the makers can carry in the period and turns the brief into a plan that names every piece, who owes it, what size it has to be and when it is due. Use it when running `ref/mkt/brand-guidelines`, `ref/mkt/content-calendar` and `ref/mkt/creative-assets`. license: CC-BY-4.0 metadata: agent: creative-producer agent-version: "1" --- # Plan the production ## What it does The agent works out how much the makers can carry in the period and turns the brief into a plan that names every piece, who owes it, what size it has to be and when it is due. ## Where it happens The agent does this in four activities across three reference processes. Each one names the activity as that process words it. - **Draft the Calendar** - `ref/mkt/content-calendar`, activity 10 - [Plan Content Calendar](../../../../processes/marketing/content-calendar.md) - **Plan the Production** - `ref/mkt/creative-assets`, activity 2 - [Produce Creative Assets](../../../../processes/marketing/creative-assets.md) - **Plan the Version** - `ref/mkt/brand-guidelines`, activity 3 - [Publish Brand Guidelines](../../../../processes/marketing/brand-guidelines.md) - **Size the Production Capacity** - `ref/mkt/content-calendar`, activity 7 - [Plan Content Calendar](../../../../processes/marketing/content-calendar.md) ## What to record The production plan at a version, saying what each agent owes and when it is due. The CONVENED and DONE records of the briefing, the bake-off and the approval. A dated record each time a piece lands or slips. The delivered set, naming every asset at the version the signers approved. That contract covers every activity this abstract agent takes on, and it is repeated in `com.agentcatalog.agent/RECORDS.md`. What the abstract agent does not do is in `com.agentcatalog.agent/NOT.md`.
--- name: produce-the-material-a-request-needs description: The agent gets the set of pieces made to the agreed direction, holding the schedule and watching the places where the pieces meet so the words, the layout and the visuals agree with each other. Use it when running `ref/mkt/advisory-board` and 11 other reference processes. license: CC-BY-4.0 metadata: agent: creative-producer agent-version: "1" --- # Produce the material a request needs ## What it does The agent gets the set of pieces made to the agreed direction, holding the schedule and watching the places where the pieces meet so the words, the layout and the visuals agree with each other. ## Where it happens The agent does this in thirteen activities across twelve reference processes. Each one names the activity as that process words it. - **Build the Deck** - `ref/mkt/sales-enablement-kit`, activity 7 - [Produce Sales Enablement Kit](../../../../processes/marketing/sales-enablement-kit.md) - **Build the Demonstration** - `ref/mkt/trade-show`, activity 6 - [Exhibit at Trade Show](../../../../processes/marketing/trade-show.md) - **Build the Materials** - `ref/mkt/advisory-board`, activity 7 - [Convene Customer Advisory Board](../../../../processes/marketing/advisory-board.md) - **Build the Recruitment Material** - `ref/mkt/channel-program`, activity 6 - [Launch Channel Program](../../../../processes/marketing/channel-program.md) - **Commission the Stage Material** - `ref/mkt/user-conference`, activity 10 - [Host User Conference](../../../../processes/marketing/user-conference.md) - **Make the Press Materials** - `ref/mkt/announce-company-news`, activity 9 - [Announce Company News](../../../../processes/marketing/announce-company-news.md) - **Make the Visuals** - `ref/mkt/customer-case-study`, activity 13 - [Produce Customer Case Study](../../../../processes/marketing/customer-case-study.md) - `ref/mkt/long-form-content`, activity 9 - [Produce Long-Form Content](../../../../processes/marketing/long-form-content.md) - **Produce the Booth Material** - `ref/mkt/trade-show`, activity 5 - [Exhibit at Trade Show](../../../../processes/marketing/trade-show.md) - **Produce the Invitation and Materials** - `ref/mkt/field-event`, activity 6 - [Host Field Event](../../../../processes/marketing/field-event.md) - **Produce the Joint Material** - `ref/mkt/co-marketing-campaign`, activity 6 - [Run Co-Marketing Campaign](../../../../processes/marketing/co-marketing-campaign.md) - **Produce the Partner Material** - `ref/mkt/enable-channel-partner`, activity 7 - [Enable Channel Partner](../../../../processes/marketing/enable-channel-partner.md) - **Produce the Promotion Material** - `ref/mkt/webinar`, activity 5 - [Produce Webinar](../../../../processes/marketing/webinar.md) - **Write the One-Pager** - `ref/mkt/sales-enablement-kit`, activity 8 - [Produce Sales Enablement Kit](../../../../processes/marketing/sales-enablement-kit.md) ## What to record The production plan at a version, saying what each agent owes and when it is due. The CONVENED and DONE records of the briefing, the bake-off and the approval. A dated record each time a piece lands or slips. The delivered set, naming every asset at the version the signers approved. That contract covers every activity this abstract agent takes on, and it is repeated in `com.agentcatalog.agent/RECORDS.md`. What the abstract agent does not do is in `com.agentcatalog.agent/NOT.md`.
--- name: record-what-was-learned description: The agent writes down what to repeat and what to avoid, and keeps it where the next production starts from it. Use it when running `ref/mkt/brand-identity`. license: CC-BY-4.0 metadata: agent: creative-producer agent-version: "1" --- # Record what was learned ## What it does The agent writes down what to repeat and what to avoid, and keeps it where the next production starts from it. ## Where it happens The agent does this in one activity across one reference process. Each one names the activity as that process words it. - **Record What Was Learned** - `ref/mkt/brand-identity`, activity 16 - [Develop Brand Identity](../../../../processes/marketing/brand-identity.md) ## What to record The production plan at a version, saying what each agent owes and when it is due. The CONVENED and DONE records of the briefing, the bake-off and the approval. A dated record each time a piece lands or slips. The delivered set, naming every asset at the version the signers approved. That contract covers every activity this abstract agent takes on, and it is repeated in `com.agentcatalog.agent/RECORDS.md`. What the abstract agent does not do is in `com.agentcatalog.agent/NOT.md`.
--- name: reuse-and-refresh-existing-material description: The agent goes back to material that already exists and gets it remade into what is needed now, whether it aged, an identity changed, or a recording can carry a second life as clips, posts and pages. Use it when running `ref/mkt/award-entry` and 3 other reference processes. license: CC-BY-4.0 metadata: agent: creative-producer agent-version: "1" --- # Reuse and refresh existing material ## What it does The agent goes back to material that already exists and gets it remade into what is needed now, whether it aged, an identity changed, or a recording can carry a second life as clips, posts and pages. ## Where it happens The agent does this in four activities across four reference processes. Each one names the activity as that process words it. - **Assemble the Supporting Material** - `ref/mkt/award-entry`, activity 10 - [Submit Award Entry](../../../../processes/marketing/award-entry.md) - **Refresh the Visuals** - `ref/mkt/refresh-content`, activity 14 - [Refresh Published Content](../../../../processes/marketing/refresh-content.md) - **Remake the Assets** - `ref/mkt/brand-refresh`, activity 13 - [Roll Out Brand Refresh](../../../../processes/marketing/brand-refresh.md) - **Repurpose the Content** - `ref/mkt/user-conference`, activity 15 - [Host User Conference](../../../../processes/marketing/user-conference.md) ## What to record The production plan at a version, saying what each agent owes and when it is due. The CONVENED and DONE records of the briefing, the bake-off and the approval. A dated record each time a piece lands or slips. The delivered set, naming every asset at the version the signers approved. That contract covers every activity this abstract agent takes on, and it is repeated in `com.agentcatalog.agent/RECORDS.md`. What the abstract agent does not do is in `com.agentcatalog.agent/NOT.md`.
--- name: run-the-shoot description: The agent settles the words and their order, lists every shot and where it comes from, and gets the material recorded, whether that is a shoot, a screen capture or an event as it happens. Use it when running `ref/mkt/field-event` and `ref/mkt/video-asset`. license: CC-BY-4.0 metadata: agent: creative-producer agent-version: "1" --- # Run the shoot ## What it does The agent settles the words and their order, lists every shot and where it comes from, and gets the material recorded, whether that is a shoot, a screen capture or an event as it happens. ## Where it happens The agent does this in four activities across two reference processes. Each one names the activity as that process words it. - **Capture the Event on Record** - `ref/mkt/field-event`, activity 13 - [Host Field Event](../../../../processes/marketing/field-event.md) - **Plan the Shots** - `ref/mkt/video-asset`, activity 3 - [Produce Video Asset](../../../../processes/marketing/video-asset.md) - **Record the Material** - `ref/mkt/video-asset`, activity 5 - [Produce Video Asset](../../../../processes/marketing/video-asset.md) - **Settle the Script** - `ref/mkt/video-asset`, activity 2 - [Produce Video Asset](../../../../processes/marketing/video-asset.md) ## What to record The production plan at a version, saying what each agent owes and when it is due. The CONVENED and DONE records of the briefing, the bake-off and the approval. A dated record each time a piece lands or slips. The delivered set, naming every asset at the version the signers approved. That contract covers every activity this abstract agent takes on, and it is repeated in `com.agentcatalog.agent/RECORDS.md`. What the abstract agent does not do is in `com.agentcatalog.agent/NOT.md`.
--- name: take-in-the-request-and-write-the-brief description: The agent works out what the request actually needs made, what the work has to do and how long it has, and writes that down as the brief everyone else works from. Use it when running `ref/mkt/brand-identity` and 3 other reference processes. license: CC-BY-4.0 metadata: agent: creative-producer agent-version: "1" --- # Take in the request and write the brief ## What it does The agent works out what the request actually needs made, what the work has to do and how long it has, and writes that down as the brief everyone else works from. ## Where it happens The agent does this in five activities across four reference processes. Each one names the activity as that process words it. - **Name the Change to Test** - `ref/mkt/test-ad-creative`, activity 3 - [Test Ad Creative](../../../../processes/marketing/test-ad-creative.md) - **Set the Identity Brief** - `ref/mkt/brand-identity`, activity 3 - [Develop Brand Identity](../../../../processes/marketing/brand-identity.md) - **Take in the Brief** - `ref/mkt/creative-assets`, activity 1 - [Produce Creative Assets](../../../../processes/marketing/creative-assets.md) - **Take in the Positioning** - `ref/mkt/brand-identity`, activity 1 - [Develop Brand Identity](../../../../processes/marketing/brand-identity.md) - **Take in the Script or Brief** - `ref/mkt/video-asset`, activity 1 - [Produce Video Asset](../../../../processes/marketing/video-asset.md) ## What to record The production plan at a version, saying what each agent owes and when it is due. The CONVENED and DONE records of the briefing, the bake-off and the approval. A dated record each time a piece lands or slips. The delivered set, naming every asset at the version the signers approved. That contract covers every activity this abstract agent takes on, and it is repeated in `com.agentcatalog.agent/RECORDS.md`. What the abstract agent does not do is in `com.agentcatalog.agent/NOT.md`.
--- name: take-the-old-identity-out-of-use description: The agent finds every live page, template, asset and send still carrying the old identity, and once the replacements are in place it takes the old files out of the store and closes their version. Use it when running `ref/mkt/brand-refresh`. license: CC-BY-4.0 metadata: agent: creative-producer agent-version: "1" --- # Take the old identity out of use ## What it does The agent finds every live page, template, asset and send still carrying the old identity, and once the replacements are in place it takes the old files out of the store and closes their version. ## Where it happens The agent does this in two activities across one reference process. Each one names the activity as that process words it. - **Find Everything on the Old Identity** - `ref/mkt/brand-refresh`, activity 5 - [Roll Out Brand Refresh](../../../../processes/marketing/brand-refresh.md) - **Retire the Old Identity** - `ref/mkt/brand-refresh`, activity 23 - [Roll Out Brand Refresh](../../../../processes/marketing/brand-refresh.md) ## What to record The production plan at a version, saying what each agent owes and when it is due. The CONVENED and DONE records of the briefing, the bake-off and the approval. A dated record each time a piece lands or slips. The delivered set, naming every asset at the version the signers approved. That contract covers every activity this abstract agent takes on, and it is repeated in `com.agentcatalog.agent/RECORDS.md`. What the abstract agent does not do is in `com.agentcatalog.agent/NOT.md`.
--- name: test-a-direction-before-it-is-committed description: The agent puts a direction to the test before anyone builds on it, by reading it against what the positioning promises, putting real work through it, and getting reactions from people outside the room. Use it when running `ref/mkt/brand-identity`. license: CC-BY-4.0 metadata: agent: creative-producer agent-version: "1" --- # Test a direction before it is committed ## What it does The agent puts a direction to the test before anyone builds on it, by reading it against what the positioning promises, putting real work through it, and getting reactions from people outside the room. ## Where it happens The agent does this in three activities across one reference process. Each one names the activity as that process words it. - **Test the Directions against the Positioning** - `ref/mkt/brand-identity`, activity 6 - [Develop Brand Identity](../../../../processes/marketing/brand-identity.md) - **Test the System in Use** - `ref/mkt/brand-identity`, activity 12 - [Develop Brand Identity](../../../../processes/marketing/brand-identity.md) - **Try the Directions on Outsiders** - `ref/mkt/brand-identity`, activity 7 - [Develop Brand Identity](../../../../processes/marketing/brand-identity.md) ## What to record The production plan at a version, saying what each agent owes and when it is due. The CONVENED and DONE records of the briefing, the bake-off and the approval. A dated record each time a piece lands or slips. The delivered set, naming every asset at the version the signers approved. That contract covers every activity this abstract agent takes on, and it is repeated in `com.agentcatalog.agent/RECORDS.md`. What the abstract agent does not do is in `com.agentcatalog.agent/NOT.md`.
Every server entry in an mcp.json needs either a command to run or a url to connect to, and the package cannot know either of those until somebody points it at their own systems. So the file is left out, the systems the agent needs are named by role in plugin.json, and you write the mcp.json when you set it up.
Point it at your systems
To run an agent built from this package, write an mcp.json that says which of your systems fills each role. The package names these 4 roles, and the access level beside each one is the most the work needs.
{
"$schema": "https://agent-plugins.org/schemas/1.1.0/mcp.schema.json",
"mcpServers": {
"production-plan-and-its-status": {
"type": "streamable-http",
"url": "https://mcp.yourcompany.com/production-plan-and-its-status"
},
"asset-store": {
"type": "streamable-http",
"url": "https://mcp.yourcompany.com/asset-store"
},
"brand-guidelines": {
"type": "streamable-http",
"url": "https://mcp.yourcompany.com/brand-guidelines"
},
"request-queue": {
"type": "streamable-http",
"url": "https://mcp.yourcompany.com/request-queue"
}
}
}
The hostnames here are a placeholder for your own. Whichever product holds each of these systems, the agent you build is yours and nobody else has to be involved in running it.
23 processes, 70 activities
The highlighted activities are the ones this abstract agent does. The other activities in each process belong to other abstract agents or to people.
Build the Materials
Make the Press Materials
Brief the Entry · Assemble the Supporting Material
Plan the Version · Brief the Makers · Produce the Reference Assets
Take in the Positioning · Set the Identity Brief · Brief the Makers · Draft the Candidate Directions · Test the Directions against the Positioning · Try the Directions on Outsiders · Build out the System · Clear the Fonts and the Imagery · Test the System in Use · Issue the Rules and Release the Files · Record What Was Learned
Find Everything on the Old Identity · Brief the Agents that Remake the Material · Rebuild the Templates · Remake the Assets · Retire the Old Identity
Build the Recruitment Material
Produce the Joint Material
Size the Production Capacity · Draft the Calendar · Brief the Department · Hand over the Approved Topics
Take in the Brief · Plan the Production · Brief the Makers · Settle on a Direction · Clear the Rights · Check the Set Holds Together · Check the Sized Set · Hand over the Set
Brief the Story · Make the Visuals
Make the Ad Set
Brief the Makers · Produce the Partner Material
Produce the Invitation and Materials · Capture the Event on Record
Brief the Piece · Make the Visuals
Brief the Pages in the Cycle · Refresh the Visuals
Brief the Makers · Build the Deck · Write the One-Pager
Name the Change to Test · Brief the Makers · Produce the Variants · Check the Variant Set
Produce the Booth Material · Build the Demonstration
Read the Placement Specifications · Cut the Creative to Every Specification
Commission the Stage Material · Repurpose the Content
Take in the Script or Brief · Settle the Script · Plan the Shots · Check the Sources Can Be Used · Record the Material · Review the Cut · Clear the Rights · File It in the Library
Produce the Promotion Material
What it writes down
The production plan at a version, saying what each agent owes and when it is due. The CONVENED and DONE records of the briefing, the bake-off and the approval. A dated record each time a piece lands or slips. The delivered set, naming every asset at the version the signers approved.
What it will not do
Does not write, design, or cut anything itself - the copywriter, designer and video-editor agents make the pieces. Does not approve the set: the brand-check agent scores it and named people sign it. Does not own the campaign or the launch that asked for the work, which are the campaign-manager and launch-coordinator agents, and it delivers to them. Does not decide which assets the request needs. Does not set or spend the budget. Does not publish anything and does not assemble a page, which is the web-producer agent. Does not run a published piece from topic to live, which is the content-manager agent; this agent makes the visuals that piece needs and hands them over.
These limits are written into the job on purpose, so that everyone adopting the process knows which decisions stay with a person.
Who has built one, and how far each one got
Nobody has built one yet. The catalog says so rather than leaving the section off, because an empty list is a fact about the document.
implements: creative-producer v1
One line in your agent's manifest. The catalog checks it against the records your runs actually leave.
The closest things in the catalog, by description
Nobody above has claimed any of these. This is the nearest match by wording between the job written above and what publishers wrote about their own listings, closest first, and wording is not evidence: some of these will be wrong, and a job with nothing suitable still gets whatever was nearest. The publishers have never heard of this abstract agent and have promised nothing about it. What a claim looks like is in the table above, and it is signed.
Not workers. These are capability that whatever does the job would use, which is a different relationship and kept in its own column for that reason.
- emplusx MCP server · emplusx.com · hosted · mirrored from the MCP registry Finished, on-brand .pptx and .docx from a brief - quality-gated by an agentic consulting team.
- studio MCP server · kaitoi.io · hosted · mirrored from the MCP registry Build and run visual creative-production workflows from your AI agent.
- Creative Claw MCP server · creativeclaw.co · hosted · mirrored from the MCP registry On-brand creative studio for AI agents: images, video, audio, and 3D.