route-approvals — Claude Code command for post approvals
route-approvals is a Claude Code command that assigns reviewers to scheduled social posts, gathers edits, and tracks sign-off before publication.
Apache-2.0 ★ 450 updated 2026-04-03
.claude/commands/route-approvals.mdWhat route-approvals does
Provide a calendar, a review mode, and the groups that need to approve the posts. The command sorts content by channel and pillar, flags sensitive items, assigns reviewers, and creates tasks in a project tool with due dates. You can add notes about context or risks.
It then gathers comments and edit requests, tags asset owners, records changes, and updates calendar status. The outputs include an approval tracker, a feedback log, and a summary for the publishing team. Asset version control runs through a DAM; the workflow also invokes asset-coordinator, brand-guardrails, and calendar-governance before sign-off.
What it helps with
- route calendar posts to the right approval groups
- create review tasks with due dates
- send requested edits to asset owners
- record approval status and prepare a sign-off summary
Example prompts for the agent
- Route the “Q2 Product Story” calendar for async review by legal, brand, and regional stakeholders.
- Prepare
spring-launchfor live review, set Friday as the deadline, and include a note about risks.
How to install route-approvals
Manually: put the files in place
.claude/commands/route-approvals.mdCall it with /route-approvals. For all projects use ~/.claude/commands/
Manually: put the files in place
~/.codex/prompts/route-approvals.mdCall it with /prompts:route-approvals. Codex marks this format deprecated in favour of skills
Manually: put the files in place
.github/prompts/route-approvals.prompt.mdManually: put the files in place
.gemini/commands/route-approvals.tomlGemini stores commands as TOML: the prompt text goes into the prompt field
Questions about route-approvals
How do I install route-approvals in Claude Code?
Create the command file at .claude/commands/route-approvals.md.
What does route-approvals do?
It coordinates review of scheduled social posts, captures requested changes, and updates calendar status. It also sends a summary of ready-to-schedule posts and outstanding risks.
Which reviewer groups can route-approvals handle?
You can pass legal, brand, PR, partner, or regional groups through the stakeholders parameter.
Source text
route-approvals.md · Apache-2.0
--- name: route-approvals description: Coordinates legal, brand, partner, and regional approvals for scheduled social content. usage: /social-scheduler-orchestration:route-approvals --calendar "Q2 Product Story" --mode async --stakeholders "legal,brand,regional" --- # Command: route-approvals ## Inputs - **calendar** – reference name or ID of the calendar produced by `plan-calendar`. - **mode** – live | async review workflow. - **stakeholders** – comma-separated list of approver groups (legal, brand, PR, partner, regional). - **deadline** – due date/time for approvals to be completed. - **notes** – optional context or risk flags requiring special review. ## Workflow 1. **Prep Packet** – generate review doc with posts grouped by channel/pillar, highlighting sensitive items. 2. **Approval Routing** – assign reviewers, create tasks in project tool, provide clear expectations + due dates. 3. **Feedback Capture** – collect comments, requested edits, or escalations; tag asset owners. 4. **Resolution & Logging** – document changes, update calendar status, ensure version control in DAM. 5. **Final Sign-off** – send summary with ready-to-schedule posts and outstanding risks. ## Outputs - Approval tracker with status, reviewer, timestamp, and required edits per post. - Consolidated feedback log + action items for asset owners. - Sign-off summary sent to publishing team and stakeholders. ## Agent/Skill Invocations - `asset-coordinator` – manages asset updates and metadata. - `brand-guardrails` skill – enforces brand/legal rules before sign-off. - `calendar-governance` skill – ensures blackout dates/geo requirements remain compliant. ---
© gtmagents · Apache-2.0 · gtmagents/gtm-agents