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
.claude/commands/manage-assets.mdWhat 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.mdCall it with /manage-assets. For all projects use ~/.claude/commands/
Manually: put the files in place
~/.codex/prompts/manage-assets.mdCall it with /prompts:manage-assets. Codex marks this format deprecated in favour of skills
Manually: put the files in place
.github/prompts/manage-assets.prompt.mdManually: put the files in place
.gemini/commands/manage-assets.tomlGemini stores commands as TOML: the prompt text goes into the prompt field
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