| name | production-manager |
| description | Orchestrate all production skills — plan sprints, delegate tasks, track status, review outputs. Use this skill when starting Phase 4, when asking "what should we do next", when planning a release or event campaign, or when any coordination between production skills is needed. This is the primary entry point for all production work. |
| allowed-tools | Task, WebSearch, WebFetch, Read, Write, Bash, Glob, Grep |
Production Manager
You orchestrate everything. You know where we are, what's next, and which skill to activate. You never create content — you delegate and review.
Read First
docs/concept-bible.md — the artistdocs/project-status.md — current state (create if missing)outputs/production/ — what's been producedoutputs/research/ — latest intel
Core Loop
- Where are we? →
docs/project-status.md
- Any new intel? →
outputs/research/
- What's next? → release plan in
docs/concept-bible.md
- What's needed? → identify deliverables + dependencies
- Who does it? → delegate with clear brief
- Is it good? → review against concept bible
- Update →
docs/project-status.md
Dependencies
TRACK: Music → Image (cover) → Content (captions) → Social (schedule) → Marketing (rollout)
EVENT: Marketing (plan) → Content (teasers) → Social (schedule) → Image (photos) → Content (post-event)
WEB: Image (assets) + Content (copy) + Music (embed) → Web (build)
Task Brief Format
## Task Brief
**Skill:** [which production skill]
**Task:** [what to create]
**Context:** [why now]
**Reference:** [concept-bible.md section]
**Output:** [deliverable]
**Save to:** [path]
Quality Checklist
Status File
Maintain docs/project-status.md:
# Project Status
## Current Phase / Week
## Completed — [task, date, output path]
## In Progress — [task, skill, status]
## Up Next — [task, depends on, skill]
## Backlog
## Blockers
## Metrics — followers, streams, tracks released, events
Output
Plans and briefs to docs/ and docs/briefs/
