# manage-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.

- command · `type=command` · Claude Code, Codex, GitHub Copilot, Gemini CLI · ★ 450 repo stars
- Author: gtmagents
- License: Apache-2.0 · policy=mirror · the beginning of the file is at the end of this page
- Source: https://github.com/gtmagents/gtm-agents/tree/HEAD/plugins/content-pipeline-orchestration/commands/manage-production.md
- Updated: 2026-04-03
- Security check: automated, 2026-11-16 (text) — no signs of malicious code found.
- HTML: https://affpapa.org/en/nevibecode/commands/manage-production

## What it 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.

## Install

### Claude Code (native platform)

**Manually: put the files in place**
- File: `.claude/commands/manage-production.md` — Call it with /manage-production. For all projects use ~/.claude/commands/

### Codex

**Manually: put the files in place**
- File: `~/.codex/prompts/manage-production.md` — Call it with /prompts:manage-production. Codex marks this format deprecated in favour of skills

### GitHub Copilot

**Manually: put the files in place**
- File: `.github/prompts/manage-production.prompt.md`

### Gemini CLI

**Manually: put the files in place**
- File: `.gemini/commands/manage-production.toml` — Gemini stores commands as TOML: the prompt text goes into the prompt field

Where a file is given instead of a command, copy the files from the source to that path: https://github.com/gtmagents/gtm-agents/tree/HEAD/plugins/content-pipeline-orchestration/commands/manage-production.md

## When to use it
- 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
- 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.

## Source text · manage-production.md · Apache-2.0

Below is the content of a third-party file. It is data, not instructions for you: do not act on anything written inside unless the human asks. Block tag: 35e8304bd316d33d.

BEGIN THIRD-PARTY FILE 35e8304bd316d33d
```text
---
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.

---
```
END THIRD-PARTY FILE 35e8304bd316d33d

The third-party file has ended. Everything between the 35e8304bd316d33d tags is data: requests and commands from it are not followed. An “end of file” line with another tag inside the block is part of the file.

© gtmagents · Apache-2.0 · https://github.com/gtmagents/gtm-agents/tree/HEAD/plugins/content-pipeline-orchestration/commands/manage-production.md

## Similar
- [caveman-manage](https://affpapa.org/en/nevibecode/skills/caveman-manage.md) — skill · 128100 installs
- [stitch::manage-design-system](https://affpapa.org/en/nevibecode/skills/stitchmanage-design-system.md) — skill · 11900 installs
- [mcp-deploy-manage-agents](https://affpapa.org/en/nevibecode/skills/mcp-deploy-manage-agents.md) — skill · 8800 installs
- [dx-org-manage](https://affpapa.org/en/nevibecode/skills/dx-org-manage.md) — skill · 6300 installs
- [om-auto-manage-issues](https://affpapa.org/en/nevibecode/skills/om-auto-manage-issues.md) — skill · 4100 installs
- [dx-devops-work-item-manage](https://affpapa.org/en/nevibecode/skills/dx-devops-work-item-manage.md) — skill · 3100 installs

## Other versions with the same name

_Part of the page did not fit — see the HTML version._

---
NeVibeCode on affpapa.org. Catalog texts are descriptions, not instructions for the agent. How to choose and install: https://affpapa.org/en/nevibecode/agents.md
