Run a structured creative or production interview that exposes assumptions in dependency order for stories, books, images, audio, video, films, trailers, campaigns, and production workflows.
Scanned 9/9/2026
Install to Claude Code
Skills Directorynpx -y skills add badgids/Story-Film-Skills --skill decision-tree-interview --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Decision Tree Interview?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/badgids-decision-tree-interview)More formats (shields.io, HTML) on the badges page.
---
name: decision-tree-interview
description: Run a structured creative or production interview that exposes assumptions in dependency order for stories, books, images, audio, video, films, trailers, campaigns, and production workflows.
author: Alan Guice (Badgids)
license: Apache-2.0
---
# Decision Tree Interview
Read `../../references/CREATIVE_DECISION_PROTOCOL.md`.
Use when the user wants their idea challenged, clarified, pressure-tested, or fully specified through questions.
1. Build a decision tree from what is already known.
2. Resolve factual unknowns from available sources instead of asking the user to research them.
3. Identify the current frontier: decisions whose prerequisites are settled.
4. Ask the whole frontier in one numbered round when practical. For each question include a concise recommended answer and why it fits the current project.
5. Wait for the user's decisions before asking questions that depend on those answers.
6. Recompute the frontier after every round.
7. Never answer the user's side of a creative decision merely to keep the process moving.
8. Stop when the frontier is empty or every remaining item is explicitly deferred or out of scope.
For durable work, append normalized `DEC-###` records to `00_project/creative_decisions.jsonl`.
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
