Create and validate professional film-production and release documents in XLSX, DOCX, and PDF formats, including trackers, call sheets, schedules, budgets, cue sheets, director books, press kits, festival packets, and campaign calendars.
Scanned 9/9/2026
Install to Claude Code
Skills Directorynpx -y skills add badgids/Story-Film-Skills --skill production-documents --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Production Documents?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/badgids-production-documents)More formats (shields.io, HTML) on the badges page.
---
name: production-documents
description: Create and validate professional film-production and release documents in XLSX, DOCX, and PDF formats, including trackers, call sheets, schedules, budgets, cue sheets, director books, press kits, festival packets, and campaign calendars.
disable-model-invocation: true
author: Alan Guice (Badgids)
license: Apache-2.0
---
# Production Documents
1. Read `../../references/PRODUCTION_DOCUMENTS.md` and the authoritative project artifacts for the requested document.
2. Add a `DOC-###` record to `00_project/document_manifest.json`.
3. Use project-relative source and output paths.
4. Use XLSX for structured tracking/calculation, DOCX for editable prose/tables, and PDF for fixed delivery/review.
5. Keep formulas as formulas and label assumptions.
6. Create documents with `scripts/production_documents.py`; it must also create the same-basename Markdown companion beside every XLSX, DOCX, or PDF output.
7. Read `../../references/DOCUMENT_COMPANIONS.md` and run `scripts/document_companions.py audit` before delivery. Run structural QC and, where available, recalc or visual preview checks.
8. Add public-facing documents to the release manifest when requested.
Done when the rich document and its human-readable Markdown companion both exist, the document opens structurally, and both are traceable to the same project sources.
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!
Ultra-compressed communication mode. Cuts token usage ~75% by speaking like caveman while keeping full technical accuracy. Supports intensity levels: lite, full (default), ultra, wenyan-lite, wenyan-full, wenyan-ultra. Use when user says "caveman mode", "talk like caveman", "use caveman", "less tokens", "be brief", or invokes /caveman. Also auto-triggers when token efficiency is requested.
Adversarial multi-agent planning skill. Self-orchestrates 5 hostile category members (unspecified-low, unspecified-high, deep, ultrabrain, artistry) via team-mode for ruthless cross-critique debate, distills only the defensible insights, then MANDATORILY hands the distilled insight bundle to the `plan` agent for executable plan formalization. Use when planning needs maximum rigor and surfacing of weak assumptions, blind spots, and over-engineering. Triggers: 'hyperplan', 'hpp', '/hyperplan', ...
Routes multi-tool workflows through MCP servers for large datasets and pipelines. Use when Bash tool overhead is limiting throughput on data-heavy tasks.
Recovers prior coding-agent session context by running `catchup <agent> --since-compact`, which extracts a clean summary of a previous Codex, Claude Code, Antigravity, OpenCode, or Pi Agent session. Use when the user says "catch up", "what did the last session do", "get me up to speed", "I switched agents", or asks to recover/summarize a previous session before continuing. Do NOT use for the current conversation, git history, or any non-agent log.
A comprehensive mathematical reasoning skill for AI assistants — handles arithmetic to research-level problems with rigorous step-by-step reasoning, systematic verification, and transparent uncertainty handling
