Skip to main content
command CX Codex

manage-production · gtmagents, content-pipeline-orchestration — Claude Code command for content production

The manage-production command turns a campaign and its assets into a production tracker with owners, review steps, and QA. Use it to plan work across several deliverables.

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-production.md
Open on GitHub

What manage-production does

For each asset, the command lays out tasks such as drafting, design, review, localization, and QA. It produces a tracker with owners, statuses, due dates, dependencies, and comments, plus a QA evidence log template and an asset handoff checklist. The plan JSON is saved or updated under .claude/plans.

Pass a pillar and a comma-separated assets list. Optional inputs cover tools or platforms and the regions or languages that need localization; QA is enabled by default. The plan records task order, parallel groups, handoff requirements, and success criteria. Failed QA can be retried up to two times. If QA defects, brand issues, or missed deadlines breach guardrails twice in 48h, the workflow calls for escalation, so teams should account for that threshold.

What it helps with

  • break a campaign into tasks for each asset
  • assign production owners and due dates
  • schedule review checkpoints and consolidate feedback
  • prepare a QA log and asset handoff checklist
  • record dependencies in a production plan

Example prompts for the agent

  • Create a production plan for AI readiness with assets ebook,video,design kit.
  • Build a tracker for AI readiness and include localization for the required regions and languages.
  • Plan production for this campaign with QA checks and a handoff checklist.

How to install manage-production

Manually: put the files in place

.claude/commands/manage-production.md

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

Questions about manage-production

How do I install manage-production in Claude Code?

Save the command file as .claude/commands/manage-production.md in your project. Then invoke it with /content-pipeline-orchestration:manage-production.

What does manage-production do?

It creates a production plan with asset-level tasks, owners, deadlines, feedback checkpoints, and QA steps. The outputs also include a QA log template and a handoff checklist.

What inputs does the command accept?

Provide pillar and a comma-separated assets list. You can also add tools or platforms and localization regions or languages; QA defaults to enabled.

Source text

manage-production.md · Apache-2.0
---
name: manage-production
description: Generates a production tracker with tasks, owners, feedback cycles, and QA steps.
usage: /content-pipeline-orchestration:manage-production --pillar "AI readiness" --assets "ebook,video,design kit"
---

# Command: manage-production

## Inputs
- **pillar** – reference pillar or campaign.
- **assets** – comma-separated asset types or names.
- **tools** – optional tools/platforms (Docs, Figma, Notion, CMS).
- **qa** – include QA/evidence plan (default true).
- **localization** – regions/languages requiring localization.

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

- **Pattern selection**: Production typically runs **pipeline** (tasks → owners → feedback → QA → packaging). Use **diamond** when localization or QA evidence can run parallel; document choice in the plan header.
- **Plan schema**: Save or update `.claude/plans/plan-<timestamp>.json` with task IDs, asset references, tooling context, parallel groups, handoff requirements, error handling, and success criteria (on-time %, defect ceiling).
- **Tool hooks**: Reference `docs/gtm-essentials.md` stack (Serena for CMS automation patches, Context7 for brand/legal standards, Sequential Thinking for retros, Playwright for accessibility/QA screens).
- **Guardrails**: Default retry limit = 2 for failed QA; escalation ladder = Creative Producer → Editorial Director → Marketing Director.
- **Review**: Run `docs/usage-guide.md#orchestration-best-practices-puerto-parity` before execution to confirm agents, dependencies, deliverables.

## Workflow
1. **Task Breakdown** – create tasks per asset (draft, design, review, localization, QA).
2. **Owner Assignment** – map writers, designers, reviewers, approvers, and due dates.
3. **Feedback Loops** – schedule review checkpoints, consolidate feedback instructions.
4. **QA Checklist** – ensure brand, accessibility, legal, and technical requirements are validated.
5. **Asset Packaging** – outline final delivery steps (naming conventions, metadata, storage paths).

## Outputs
- Production tracker (task, owner, status, due date, dependencies, comments).
- QA/evidence log template.
- Asset handoff checklist with storage locations.
- Plan JSON entry stored/updated in `.claude/plans` for audit trail.

## Agent/Skill Invocations
- `creative-producer` – runs production board + QA.
- `asset-tracking` skill – ensures dependencies + metadata.
- `distribution-lead` – receives handoff package for publishing.

## GTM Agents Safeguards
- **Fallback agents**: document substitutes (e.g., Editorial Director covering Creative Producer) when specialists unavailable.
- **Escalation triggers**: if QA defects, brand issues, or missed deadlines breach guardrails twice in 48h, escalate to Content + Growth leadership per GTM Agents runbook.
- **Plan maintenance**: update plan JSON and change log whenever assets, owners, or QA scope shift so audit trail mirrors GTM Agents standards.

---

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

Similar slash commands

All slash commands for Agent setup: memory, context, orchestration →

manage-production by other authors comes first.

manage-production gtmagents manage-production turns a list of creative assets into a production plan with tasks, owners, due dates and QA checkpoints, plus a board template. CX Codex +1 ★ 450repo stars caveman-manage JuliusBrussee caveman-manage is a skill that checks Caveman Cloud experiment state and evidence, recommends one action, or blocks unsafe requests. It runs before lifecycle decisions. CX Codex +1 128,100installs stitch::manage-design-system official google-labs-code stitch::manage-design-system is a Claude Code skill that builds design systems in Stitch and applies them to screens. It runs when a project needs design tokens created or updated. CX Codex +1 11,900installs mcp-deploy-manage-agents official github mcp-deploy-manage-agents is a GitHub Copilot skill for deploying MCP agents in Microsoft 365 and controlling their access. It covers admin review, user assignments, and security checks. CX Codex +1 8,800installs dx-org-manage forcedotcom The dx-org-manage Claude Code skill runs Salesforce org operations through sf. It creates scratch orgs, lists or resumes them, removes them, and opens orgs in a browser. CX Codex +1 6,300installs om-auto-manage-issues open-mercato The om-auto-manage-issues Claude Code skill triages existing tracker issues and clarifies their requirements. It adds missing SDLC labels, checks Definition of Ready, and posts analysis as a comment. CX Codex +1 4,100installs dx-devops-work-item-manage forcedotcom dx-devops-work-item-manage — a Claude Code skill that manages the full lifecycle of DevOps Center work items. Runs when tracking, creating, or updating tasks, committing changes, and opening PRs. CX Codex +1 3,100installs

From the same set224

The whole set →
qualify-lead qualify-lead scores buyer fit and intent signals to determine whether sales teams should route, nurture, or recycle an account. CX Codex +1 ★ 450repo stars technical-seo This skill guides technical SEO checks for crawl and index problems, performance regressions, and structured data gaps. Use it when reviewing a site migration or investigating SEO issues. CX Codex +1 ★ 450repo stars creative-iteration-playbook creative-iteration-playbook turns social creative work into briefs, test matrices, a production pipeline and stop thresholds for paid campaigns. CX Codex +1 ★ 450repo stars plan-loyalty plan-loyalty generates a loyalty program blueprint with tier structures, customer incentives, and lifecycle triggers within a set budget. CX Codex +1 ★ 450repo stars design-referral design-referral is a Claude Code command that designs referral programs with incentives, rules, and governance, producing a charter, stakeholder deck, and risk log. CX Codex +1 ★ 450repo stars design-nurture design-nurture builds multi-stage nurture journey blueprints with audience segmentation, triggers, and a content plan. Useful for planning lifecycle marketing and RevOps campaigns. CX Codex +1 ★ 450repo stars run-launch The run-launch command builds a launch execution plan with a timeline, communications, monitoring, and go/no-go gates. Use it to coordinate channel work and launch-day operations. CX Codex +1 ★ 450repo stars build-model The build-model command builds a data modeling plan: transforms, tests, deployment schedule and dependencies for analytics use cases. CX Codex +1 ★ 450repo stars

Project sponsors

Companies that keep this analytics open