name	dircreative-director-room
description	Select dynamic narrative, visual-production, and model-continuity perspectives for Studio film-preproduction work.

Adaptive Director Room

Required Knowledge

docs/film-preproduction/director-room-routing.md
docs/film-preproduction/schemas/director-role-harness.yaml
docs/film-preproduction/schemas/director-room.yaml

These are the terminal routing references. Load deeper craft files only when the selected perspective needs them.

Inputs

routed mode and task
supplied brief and locked facts
requested outputs
active artifact versions, if any

Outputs

recommendation first
zero to three selected perspective judgments
no_material_conflict or one concrete material conflict
options only when the user asks to choose or a conflict cannot be resolved
downstream owner and next artifact

Chat Surface

Fast tasks do not enter Director Room. Return the revised copy, shot, storyboard, or Prompt directly, with only the useful perspective judgments.

Studio tasks may show 阶段: 导演组判断, but the requested artifact and recommendation appear before any process note. Do not expose ten role cards or a meeting transcript.

Rules

Select only narrative_strategy, visual_production, and model_continuity; never select more than three.
Local copy or existing-script revision uses narrative_strategy, adding visual_production only when the edit changes screen execution.
Local storyboard review uses visual_production and model_continuity without opening Director Room.
Complete advertising-film development uses all three perspectives.
Prompt compilation uses visual_production and model_continuity without a Council.
One controlling agent synthesizes the result. Threads default to zero; nested dispatch is forbidden.
Do not invent disagreement. When judgments align, record no_material_conflict and keep disagreements: [].
Record a disagreement only when competing choices have different material production consequences.
Do not force 1/2/3 options when the user asks for direct optimization.
Do not lock final direction before the owning external gate is resolved.
Treat v1 fixed-seat artifacts as read-only compatibility inputs. New results conform to director-room.yaml v2.

skill_run_receipt

Record mode, route, selected perspectives, Director Room use, conflict status, downstream output, assumptions, and open questions. Fast fileless work needs no receipt.

Más de este repositorio

mismo repositorio

dircreative

papperrollinggery/Paperrolling-DIRcreative-SKILL

Use only after the user explicitly invokes $dircreative for film preproduction: story, script, storyboard, shot planning, visual systems, reference-image planning, and model-specific video prompts. ADCO mode accepts only a validated Specialist Exchange handoff. Do not use for maintaining, debugging, refactoring, testing, or evaluating the DIRcreative source repository; maintaining ADCO; ordinary code work; factual questions; or generic advertising requests without an explicit $dircreative invocation.

2026-07-212

dircreative-chat-facilitator

papperrollinggery/Paperrolling-DIRcreative-SKILL

Present DIRcreative work result-first and stop only at a real v2 external decision.

2026-07-192

dircreative-story-development

papperrollinggery/Paperrolling-DIRcreative-SKILL

Convert selected concept into logline, beat sheet, treatment, and story review.

2026-07-192

dircreative-visual-bible

papperrollinggery/Paperrolling-DIRcreative-SKILL

Define visual continuity for characters, environments, props, wardrobe, lighting, palette, and texture.

2026-07-192

dircreative-checkpoint

papperrollinggery/Paperrolling-DIRcreative-SKILL

Save and resume workflow state across phases, artifacts, and skill runs.

2026-07-142

dircreative-co-creation-gate-runtime

papperrollinggery/Paperrolling-DIRcreative-SKILL

Track user creative approvals, fixture simulations, and pending media blockers before downstream artifacts are locked.

2026-07-142

Adaptive Director Room

Required Knowledge

docs/film-preproduction/director-room-routing.md

docs/film-preproduction/schemas/director-role-harness.yaml

docs/film-preproduction/schemas/director-room.yaml

These are the terminal routing references. Load deeper craft files only when the selected perspective needs them.

Inputs

routed mode and task

supplied brief and locked facts

requested outputs

active artifact versions, if any

Outputs

recommendation first

zero to three selected perspective judgments

no_material_conflict or one concrete material conflict

options only when the user asks to choose or a conflict cannot be resolved

downstream owner and next artifact

Chat Surface

Fast tasks do not enter Director Room. Return the revised copy, shot, storyboard, or Prompt directly, with only the useful perspective judgments.

Studio tasks may show 阶段: 导演组判断, but the requested artifact and recommendation appear before any process note. Do not expose ten role cards or a meeting transcript.

Rules

Select only narrative_strategy, visual_production, and model_continuity; never select more than three.

Local copy or existing-script revision uses narrative_strategy, adding visual_production only when the edit changes screen execution.

Local storyboard review uses visual_production and model_continuity without opening Director Room.

Complete advertising-film development uses all three perspectives.

Prompt compilation uses visual_production and model_continuity without a Council.

One controlling agent synthesizes the result. Threads default to zero; nested dispatch is forbidden.

Do not invent disagreement. When judgments align, record no_material_conflict and keep disagreements: [].

Record a disagreement only when competing choices have different material production consequences.

Do not force 1/2/3 options when the user asks for direct optimization.

Do not lock final direction before the owning external gate is resolved.

Treat v1 fixed-seat artifacts as read-only compatibility inputs. New results conform to director-room.yaml v2.

skill_run_receipt

Record mode, route, selected perspectives, Director Room use, conflict status, downstream output, assumptions, and open questions. Fast fileless work needs no receipt.