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
.claude/commands/manage-production.mdWhat 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 readinesswith assetsebook,video,design kit. - Build a tracker for
AI readinessand 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.mdCall it with /manage-production. For all projects use ~/.claude/commands/
Manually: put the files in place
~/.codex/prompts/manage-production.mdCall it with /prompts:manage-production. Codex marks this format deprecated in favour of skills
Manually: put the files in place
.github/prompts/manage-production.prompt.mdManually: put the files in place
.gemini/commands/manage-production.tomlGemini stores commands as TOML: the prompt text goes into the prompt field
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.