Skip to main content
command CX Codex

manage-assets — Claude Code command: partner asset coordination

manage-assets — a command for orchestrating co-branded asset production, approvals, and distribution across partner teams. Tracks asset inventory, routes review workflows, and packages deliverables for activation.

Apache-2.0 ★ 450 updated 2026-04-03

Install into Claude Code · Manually: put the files in place All methods and platforms ↓
.claude/commands/manage-assets.md
Open on GitHub

What manage-assets does

Orchestrates the full asset lifecycle: collects requirements from campaign definition, applies co-branding guardrails (templates, logos, disclaimers, accessibility), routes approvals through stakeholder groups (brand, legal, product, partner), versions final assets with metadata, and prepares distribution bundles with partner instructions and tracking parameters.

Follows the GTM Agents pattern—builds a dependency graph across asset repositories (Drive, Dropbox, SharePoint, DAM), task owners, and partners. Saves execution plans to .claude/plans/plan-<timestamp>.json for audit and SLA tracking. If approvals fail twice or compliance violations arise, escalates to the partner governance council per GTM Agents safeguards.

Provide the campaign name, asset repository location, approval stakeholders, and optional localization or compliance scope. The command captures evidence of all decisions and outputs an asset tracker with version history.

What it helps with

  • inventory co-branded assets and track approval status across partners
  • route asset reviews through multiple governance layers simultaneously
  • enforce co-branding and accessibility rules on all versions
  • maintain version control and metadata for each locale
  • package approved assets with activation instructions and expiration dates

Example prompts for the agent

  • /partner-co-marketing-orchestration:manage-assets --campaign "AI Launch Tour" --repo drive --approvers "brand,legal"
  • /partner-co-marketing-orchestration:manage-assets --campaign "Product Release" --repo SharePoint --approvers "legal,product,partner" --locales "en,de,ja"
  • /partner-co-marketing-orchestration:manage-assets --campaign "Q4 Promo" --repo DAM --approvers "brand" --compliance "financial"

How to install manage-assets

Manually: put the files in place

.claude/commands/manage-assets.md

Call it with /manage-assets. For all projects use ~/.claude/commands/

Questions about manage-assets

How do I install manage-assets in Claude Code?

Copy .claude/commands/manage-assets.md from the gtmagents/gtm-agents repository into your project's .claude/commands folder. The command will then be available.

What does manage-assets do?

Manages the full co-branded asset workflow: pulls asset requirements, routes reviews through partner stakeholders, enforces branding and compliance rules, versions final outputs with metadata, and prepares distribution packages with partner activation instructions.

Which approver groups can I specify?

Valid values are brand, legal, product, and partner. Pass them comma-separated to --approvers. The command routes workflows accordingly and records each decision with timestamps and evidence.

Source text

manage-assets.md · Apache-2.0
---
name: manage-assets
description: Coordinates co-branded asset production, approvals, and distribution across partners.
usage: /partner-co-marketing-orchestration:manage-assets --campaign "AI Launch Tour" --repo drive --approvers "brand,legal"
---

# Command: manage-assets

## Inputs
- **campaign** – reference campaign/program name.
- **repo** – asset repository (Drive, Dropbox, SharePoint, DAM) to track.
- **approvers** – comma-separated stakeholder groups (brand, legal, product, partner).
- **locales** – optional list of localization requirements.
- **compliance** – optional flags for regulated industries.

### GTM Agents Pattern & Plan Checklist
> Mirrors GTM Agents orchestrator blueprint @puerto/plugins/orchestrator/README.md#112-325.

- **Pattern selection**: Asset management typically runs **pipeline** (inventory → guardrails → approvals → versioning → distribution). If approvals across partners can run in parallel, document a **diamond** segment and merge gate in the plan.
- **Plan schema**: Save `.claude/plans/plan-<timestamp>.json` capturing campaign, repositories, task IDs, partner owners, dependency graph (legal, translation, DAM), error handling, and success metrics (approval SLA, asset quality, localization coverage).
- **Tool hooks**: Reference `docs/gtm-essentials.md` stack—Serena for asset diff reviews, Context7 for partner brand/legal guidance, Sequential Thinking for cross-org approval cadences, Playwright for accessibility/landing page QA if needed.
- **Guardrails**: Default retry limit = 2 for failed approvals/uploads; escalation ladder = Asset Manager → Partner Ops → Joint governance council.
- **Review**: Use `docs/usage-guide.md#orchestration-best-practices-puerto-parity` before execution to confirm owners, dependencies, deliverables.

## Workflow
1. **Inventory Setup** – pull required asset list from `co-plan-campaign`, map owners + due dates.
2. **Co-branding Guardrails** – apply templates, logos, disclaimers, and accessibility checks per partner.
3. **Approval Routing** – trigger review workflows, capture feedback, and log decisions.
4. **Version Control** – store final assets with metadata (version, locale, usage notes).
5. **Distribution** – package assets for activation teams with instructions, tracking parameters, and expiration dates.

## Outputs
- Asset tracker (status, owner, reviewer, link, compliance notes).
- Approval log referencing evidence + timestamps.
- Distribution bundle with metadata sheet and partner instructions.
- Plan JSON entry stored/updated in `.claude/plans` for audit trail.

## Agent/Skill Invocations
- `co-marketing-asset-manager` – oversees production + routing.
- `asset-approval` skill – enforces review workflows and evidence capture.
- `co-branding` skill – validates visual/messaging requirements.

## GTM Agents Safeguards
- **Fallback agents**: document substitutes (e.g., Partner Marketer covering Asset Manager) when leads unavailable.
- **Escalation triggers**: if approvals exceed SLA twice, compliance issues arise, or assets violate guardrails, escalate per GTM Agents rip-cord to partner governance committee.
- **Plan maintenance**: update plan JSON/change log whenever repositories, approvers, or compliance scopes shift.

---

© gtmagents · Apache-2.0 · gtmagents/gtm-agents

Similar slash commands

All slash commands for Marketing and content →

From the same set224

The whole set →
configure-branches The configure-branches command for Claude Code generates step-by-step instructions for configuring branching, personalization, and automations in nurture campaigns. CX Codex +1 ★ 450repo stars run-standups run-standups runs a daily MQL→SQL pipeline standup, pulling routing metrics, logging blockers and assigning follow-up actions. CX Codex +1 ★ 450repo stars connect-signals connect-signals sets up data connections, schema alignment, and monitoring for B2B intent, product, and engagement feeds. CX Codex +1 ★ 450repo stars track-source track-source combines partner campaign data and produces attribution reporting with revenue contributions and suggested changes. Use it to review co-marketing results. CX Codex +1 ★ 450repo stars optimize-referrals optimize-referrals analyzes referral conversion funnels, fraud patterns, and partner health to generate structured optimization plans in Claude Code. CX Codex +1 ★ 450repo stars synthesize-feedback The synthesize-feedback command turns customer signals into ranked themes and estimates their impact. Use it to prepare evidence and follow-up priorities from feedback. CX Codex +1 ★ 450repo stars define-handoff define-handoff — a command to design lead-to-sales handoff: sets routing rules, response SLAs, and enablement requirements for each sales pod or segment. CX Codex +1 ★ 450repo stars monitor-personalization monitor-personalization audits personalization campaigns, tracks experiment outcomes, and flags consent violations across user segments. CX Codex +1 ★ 450repo stars

Project sponsors

Companies that keep this analytics open