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.
Installs 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 with every re-scan.
[](https://www.skillsdirectory.com/skills/badgids-decision-tree-interview)
---
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`.
