Short Drama Scriptwriter

What it solves

Short-drama drafts often read like novels: motivation arrives through exposition, conflict depends on labels, and scenes are hard to shoot, voice over, or feed to AI image and video models. This skill targets 70- to 90-episode projects with 1- to 2-minute episodes, turning a confirmed outline into production-ready scripts and reducing continuity drift.

How it works

• Reads the outline, synopsis, or project brief, then extracts worldview, character wants, secrets, core obstacles, ending direction, and locked constraints while flagging causality gaps, platform risks, and production risks.
• When the audience is unspecified, proposes 3 to 5 audience directions and waits for confirmation before finalizing the outline.
• Applies references/format-standard.md, references/production-writing.md, and references/story-engine.md, converting abstract “cool,” “angsty,” or “romantic” beats into concrete events, actions, choices, losses, and visuals.
• Builds the cast, episodic units, long-running arcs, and a 70- to 90-episode card list, with each episode defining the opening event, conflict, stage change, and ending hook.
• Writes episodes with visible action, concise dialogue, single-line sentences, clear scenes, and a hook or reversal at the end while maintaining ledgers for character state, props, foreshadowing, and timeline.
• Runs python scripts/check_script.py --key-prop during validation, fixes errors, evaluates warnings, and keeps instructional headings out of the final script unless required.

Boundaries

It does not override user-approved mainline, relationships, or endings. References are used for structural homage, not copied protected lines or scenes. Suggestive content is limited to clearly adult characters, and profanity must be followed by 【做消音处理】. If a labeled format is required, headings appear on their own line; if the user requests the formal script, instructional labels should not appear in the final body.