This skill handles project initialization, cross-stage routing, production format, and the Dashboard. The body of each stage is completed by the corresponding owner.
Quick Start
All projects uniformly use the creator-first workflow: each episode maintains on demand
剧本.md、视觉设定.md、分镜.md、图片提示词.md、视频提示词.md, without establishing a parallel structured creative source of truth.
For the specific approach, see five creative documents。
Routing
| What the user wants to do | owner / behavior |
|---|---|
| Develop ideas, series promise, adaptation, and episode map | $short-drama-develop, only when the user needs it |
| Identify episodes from existing complete scripts/loose drafts for multiple episodes | $short-drama-develop build a temporary index according to actual boundaries |
| Analyze a long original work | $short-drama-novel-analyze, only when the user needs it |
| Write or revise a single-episode script | $short-drama-write → 剧本.md |
| Break down characters, looks, locations, and props | $short-drama-assets → 视觉设定.md |
| Write asset image prompts | $short-drama-image-prompts → 图片提示词.md |
| Do shots and freeze keyframes | $short-drama-storyboard → 分镜.md |
| Write video/timeline music prompts | $short-drama-video-prompts → 视频提示词.md |
| Actually generate media | $short-drama-produce, preview first, then explicitly confirm, and finally run |
| Edit produced materials into a final cut | $short-drama-edit → 剪辑单.md and 制作成果/成片/ |
| Review or validate | $short-drama-review, only when the user names it |
| Initialize, Dashboard, archive named documents | This skill |
项目开发/ The long-material analysis and episode indexing in are an optional analysis workspace and do not participate in single-episode layout decisions; writing any episode still only maintains
that episode's five creator-first Markdown documents.
An existing script can directly break down assets; existing visual facts can directly write image prompts or storyboards; an existing storyboard can directly write video prompts. Do not fabricate upstream just to fill in a nominal pipeline.
The five creative documents record the script, visuals, and prompts; the editing sheet records trade-offs and post-processing after asset production. When modifying the story, shot responsibilities, or upstream duration declarations, return to the document responsible for that content.
Execute the request
- Find the project or material given by the user, and read only the direct input of the current task.
- Hand the complete scope named by the user to the corresponding owner; batches only control context and automatically continue running.
- Ask only when there is a real creative fork; do not ask the creator about schema, directories, transactions, or checkers.
- After the scope is completed, report once on what was completed, key decisions, genuinely unresolved items, and optional next steps.
- Do not automatically start reviews, archiving, or production that the user has not named.
- When a request spans visual settings, image prompts, storyboards, or video prompts, perform a visual dependency reconciliation against the current five documents before finishing; do not, just because image prompts and storyboards can run in parallel, leave the later-finished branch outside the old references of the other branch.
- When a video prompt request encounters "Input reference image: none" or still carries "reference image to be added", first route the storyboard owner to check the project's existing images and refresh the binding. If there is a matching image, continue running in the same request; if a necessary image is missing, stop and list it.
When stopping, give all three paths together: put the existing images into the project and bind them as
REF-...; the creator produces images in their own tool, and for this round first usePLAN-...to write out the shot-by-shot image attachment plan and produce video prompts as usual; or explicitly switch to text-to-video. Producing reference images with this kit requires an adapter and credentials outside the project, which is only one approach for the first path—do not present it as the only entry point, and do not offer only the two options of "generate reference images / text-to-video". Do not treat "no manual specification" as an explicit choice of text-to-video. In this round, if shots still lack "visual basis", backfill according to the already finalized frozen keyframes at the same time; the two bases describe the same frame of image, so do not fill in only one. - When the user names the target video model in the session ("write for MiniMax H3", "use Seedance 2.5") and
short-drama.json'sproduction_profileor stillunset, first write this choice together with the native duration, reference method, and body language it brings into the profile, then continue to the downstream stages. If a single mention in the session is not recorded in the profile, the next round will fall back to the generic path, and the dialect and duration will have to be guessed again.
Initialization and Dashboard
Run when project configuration is needed:
python3 {技能目录}/scripts/project_tool.py init ./my-drama --title "示例短剧"
When directly entering the already confirmed creator description language, prompt language, aspect ratio, episode count, or single-episode target duration, the first init should carry the corresponding
--language、--prompt-language、--aspect-ratio、--episode-count、--target-seconds; only omit
unconfirmed items, and do not leave the definite facts in the Brief as nullin the configuration. When writing the confirmed production profile, the status is uniformly
accepted;unset only means not yet decided; do not create another intermediate status.
init only establishes the configuration and empty directories; on the first creation, the document is written into 剧集/<EP>/, and empty files are not pre-created.
When the project has already been set up and the user only later settles on the target video model, write the choice into the profile and at the same time show its impact on the duration range, reference method, and
body language. The profile only accepts published and accepted creator decisions, so it is three steps, not one. First write a line of decision record
(accepted_value is the object itself that should go into choices , do not wrap another layer of choices):
{"decision_id":"CD-H3","status":"accepted","target_locators":[{"src":"short-drama","field":"/creator_authority/production_profile/choices"}],"accepted_value":{"target_video_model":"minimax-h3","video_prompt_dialect":"minimax-h3","video_prompt_language":"en","native_duration_seconds":{"min":4,"max":15},"supported_generation_modes":["text","first_frame","first_last_frame","reference"],"audio_generation":"same_pass"}}
then publish, accept, and write:
python3 {技能目录}/scripts/project_tool.py publish <project> --owner short-drama \
--artifact-id AR-PROFILE --output "创作者决策/production-profile.jsonl=输入/profile.jsonl"
python3 {技能目录}/scripts/project_tool.py accept <project> --artifact-id AR-PROFILE --decision accepted
python3 {技能目录}/scripts/project_tool.py set-authority <project> \
--field /creator_authority/production_profile/choices \
--decision-ref "创作者决策/production-profile.jsonl#CD-H3"
The values of each field are given by the matched model dialect:$short-drama-video-prompts 's MiniMax H3 / Seedance / Wan 3.0 dialect files all write the
recommended profile. After writing, use status to review whether video_model_profile has already appeared.
For project positioning and safe writing, see Run preflight. When the user explicitly requests the Dashboard, run:
python3 {技能目录}/scripts/dashboard_server.py --workspace <workspace> --port 0 --detach --open
--detach lets the server process run independently of the current shell; the end of the session, closing the terminal, or exiting the agent will not take it away;
the link therefore remains valid throughout the entire creation period. The running address, port, and pid are recorded in
<workspace>/.short-drama/dashboard.json(readable only by the user), and the logs are in the same directory dashboard.log:
python3 {技能目录}/scripts/dashboard_server.py --workspace <workspace> --status # 打印当前链接
python3 {技能目录}/scripts/dashboard_server.py --workspace <workspace> --stop # 停止
When the same workspace already has a running Dashboard, starting it again will only print the same link and will not open a second port; if you really want to change the
port or change the token, add --restart. Without adding --detach , the behavior is unchanged: run in the foreground, ending with Ctrl-C.
The Dashboard displays the project by stage: the full-series page gives the next step and episode progress, and each episode is divided into six views: script, settings, storyboard, prompts, final cut, and review,
with ⌘K searching the whole series. The structure view is read-only; changes are saved as Markdown in "Edit Source". Images only recognize the bindings in the document:
thumbnails are the 用途:起始帧 in the storyboard's REF-..., each shot's material is the "source" of the edit list, and the final cut is the edit output; if there is no binding
a blank slot is shown, and images are not matched by filename. It is not responsible for workflow orchestration or media production; anywhere writing or generation is needed, it only copies a request sentence and hands it back to the conversation.
Each episode's target duration comes from status 's format, and rhythm comparison only uses accepted rhythm_profile。
Project-level creative decisions
When production form, visual direction, playback surface, and episode length targets do indeed constrain multiple stages, show the choices and their impact and let the user decide. Look Development is an optional branch, not a fixed gate for entering image prompts or storyboards.
Rhythm values (opening hook seconds, emotional beat interval, number of reversals, VO ratio, average shot length, etc.) live in
creator_authority.rhythm_profile. The fields and default values are proposed by $short-drama-develop according to the production form;
after the creator accepts or rewrites them, write them in according to the three steps above: the decision's accepted_value is the complete archive object,--field
write /creator_authority/rhythm_profile; after the archive has been accepted, when changing only one value, --field points to that field.
set-authority only validates type and range; missing fields, out-of-range values, or extra unknown fields are all rejected for writing. Downstream only performs arithmetic checks against archives where status is accepted , and missing,unset or
proposed all mean "not declared, not checked". After writing, use status to review rhythm_profile; when the archive is invalid after manual changes,
it returns an empty archive, with the problems listed in rhythm_profile_problems。
Read only one piece of relevant knowledge per question:
- Rule levels and owner routing:Rules and routing index
- Output language, stable IDs, ownership, and safety boundaries:Contracts and ownership
- Form differences among live action, 2D, 3D, ink wash, chibi, and Chinese animation:Production form
- When representative frames need to be compared:Look Development
- What reference images can control:Reference character
- Occlusion, delayed reveal, and when the audience knows:Audience reveal
- Responsibilities of the master, pickups, and alternate versions:Pickups and alternates
Production and delivery boundaries
External production always retains preview -> explicit confirm -> run. Archiving only copies the current documents and finished products explicitly named by the user, excluding
private inputs, credentials, absolute paths, and hidden runtime state; it does not fabricate approvals, hashes, or a second set of content for the archive.
When the user asks "how do I export/deliver it to me when it's done", use export to package the current state:
python3 {技能目录}/scripts/project_tool.py export <project> --out <项目外目录>
It copies each episode's existing five creative documents and 剧集/<EP>/制作成果/ to --out, attaching manifest.json and
checksums.sha256, and excludes 输入/、交付/ and .short-drama/. When only part is wanted, add
--episode EP001(repeatable); when only text is wanted, add --no-media; to overwrite an old directory, add --overwrite。
--out must be outside the project.
export iscurrent state snapshot, in the manifest asserts_approval is always false: it does not claim any review or
creator acceptance. The only path that still provides a formal delivery package with approval evidence is package/verify .
Installation and maintenance
Run only during installation, upgrade, or troubleshooting python3 scripts/selftest.py。