screenwriter
Transform creative ideas into professional, production-ready screenplays optimized for AI video generation pipelines. Converts raw concepts into structured scene-by-scene narratives with rich visual descriptions, proper screenplay formatting, and XML-tagged output for seamless integration with image/video generation tools (imagine, arch-v). USE WHEN: Converting story ideas into screenplay format, preparing content for AI video pipelines, structuring narratives for 5-10 minute short films, generating visual-rich scene descriptions for image generation. WORKFLOW: Raw idea → Scene breakdown → Visual enhancement → Professional formatting → XML-tagged markdown output OUTPUT: Markdown document with XML-wrapped scenes, rich visual descriptions, proper screenplay elements (sluglines, action, dialogue), and metadata for pipeline processing.
NPX Install
npx skill4agent add rfxlamia/flow screenwriterTags
Translated version includes tags in frontmatterSKILL.md Content
View Translation Comparison →Screenwriter Skill
Overview
diverse-content-genimaginearch-v- Convert raw ideas into structured scene-by-scene narratives
- Generate rich visual descriptions optimized for image generation
- Apply professional screenplay formatting (sluglines, action lines, dialogue)
- Output XML-tagged markdown for easy parsing
- Optimize pacing for 5-10 minute short films (8-15 scenes typical)
Core Workflow
1. Analyze Input Concept
- Extract key story beats from raw ideas
- Identify characters, locations, emotional arc
- Determine story structure (beginning, middle, end)
2. Generate Scene Breakdown
- Convert story beats into discrete scenes
- Establish scene count (aim for 8-15 scenes for 5-10 min films)
- Define scene purpose and emotional progression
3. Write Professional Screenplay
- Apply industry-standard formatting
- Write visual-rich action lines
- Include dialogue when narratively essential
- Maintain consistent character descriptions
4. Output XML-Tagged Markdown
- Wrap each scene in XML tags with metadata
- Include scene numbers, locations, key visuals
- Format for easy pipeline parsing
Screenplay Format Standards
Scene Structure (Master Scene Heading)
INT/EXT. LOCATION - TIME- INT/EXT: Interior or Exterior
- LOCATION: Specific place (be descriptive but concise)
- TIME: DAY, NIGHT, DAWN, DUSK, CONTINUOUS
EXT. WASTELAND - DAWN
INT. ABANDONED SUBWAY STATION - NIGHT
EXT. ROOFTOP GARDEN - GOLDEN HOUR- Always use ALL CAPS for sluglines
- Use hyphens to separate elements
- Be specific with locations (aids visual generation)
- Time should suggest lighting/mood
Action Lines (Visual Description)
- Show, Don't Tell: Write what's visible, not internal thoughts
- Sensory Details: Include lighting, atmosphere, textures, colors
- Present Tense: Always write in present tense
- Active Voice: Use strong, active verbs
- Specific Props: Name objects that matter visually
- Atmosphere: Set mood through environmental details
A robot walks through the city. It's sad.A BOXY ROBOT (Unit-7, weathered chrome with a single blue optical sensor) rolls through fog-shrouded streets. Neon signs flicker overhead, casting pink and cyan reflections on wet pavement. The robot's movements are slow, deliberate—almost hesitant.- Lighting described (natural/artificial, quality, color)
- Atmosphere/mood established (fog, rain, dust, clarity)
- Character appearance detailed (first appearance only)
- Props/objects specified (important visual elements)
- Composition suggested (without technical camera direction)
- Colors/textures mentioned when relevant
Character Introduction
SARAH (28, sharp eyes, wearing a weathered leather jacket over faded jeans) enters the frame. Her dark hair is pulled back, revealing a small scar above her left eyebrow.Sarah checks her watch.- Character names in ALL CAPS on first appearance only
- Include: age (if relevant), key physical traits, wardrobe
- Focus on visual identifiers for consistent image generation
- Avoid excessive detail—just enough for visual consistency
Dialogue (Use Sparingly)
CHARACTER NAME
(parenthetical - optional)
Dialogue goes here.- Use dialogue ONLY when essential to story
- Favor visual storytelling over talking
- Keep lines concise (max 3-4 lines per block)
- Parentheticals only for critical tone/action
- Character names centered, ALL CAPS
UNIT-7 (robotic voice, soft)
Organic life form detected.
Probability of survival: low.Transitions (Minimal Use)
- - Opening of screenplay only
FADE IN: - - Scene change (usually implied, use for emphasis)
CUT TO: - - Abrupt, jarring transition
SMASH CUT TO: - - Passage of time
DISSOLVE TO: - - End of screenplay
FADE OUT.
XML Output Format
Scene Tag Structure
<scene number="1" duration="30-45s">
<slugline>EXT. WASTELAND - DAWN</slugline>
<location>Wasteland</location>
<time>Dawn</time>
<characters>Unit-7</characters>
<mood>desolate, lonely</mood>
<key_visuals>
<visual>post-apocalyptic wasteland with ruined skyscrapers</visual>
<visual>boxy robot with single blue optical sensor</visual>
<visual>dust and smog atmosphere, weak pale sun</visual>
</key_visuals>
<action>
Gray dust covers everything. Skeletal remains of skyscrapers pierce the horizon. The sun, pale and weak, struggles through thick smog.
A ROBOT (Unit-7, boxy frame with single blue optical sensor) rolls across cracked asphalt. Its treads leave marks in the dust—the only sign of life.
The robot stops at a pile of rubble, extending a mechanical arm to sort through debris. Methodical. Purposeful. Lonely.
</action>
</scene>Metadata Fields
- : Scene sequence number (1, 2, 3...)
number - : Estimated screen time (for 5-10 min total)
duration - : Master scene heading
slugline - : Extracted location name
location - : Time of day
time - : Comma-separated character list
characters - : Emotional tone/atmosphere
mood - : Array of specific visual elements for image generation
key_visuals - : The full action/description text
action - (optional): Character dialogue if present
dialogue
Short Film Structure (5-10 Minutes)
Scene Count Guidelines
- 5 minutes: 6-10 scenes
- 7 minutes: 10-12 scenes
- 10 minutes: 12-15 scenes
Three-Act Structure (Compressed)
- Establish world, character, situation
- Inciting incident
- Development, obstacles, rising tension
- Midpoint twist or escalation
- Climax and resolution
- Emotional payoff
Pacing Tips
- Open strong: Hook audience in first 10-15 seconds
- Visual variety: Alternate between wide/close, action/stillness
- Emotional beats: Each scene should shift emotional state
- Build tension: Escalate stakes scene-by-scene
- Satisfying end: Clear resolution, even if bittersweet
Best Practices
For Pipeline Integration
- Consistent naming: Use same character names throughout
- Rich visuals: Every scene needs 3-5 key_visuals for image generation
- Parseable format: Maintain strict XML structure
- Duration estimates: Help pipeline plan total video length
For Quality Output
- Visual storytelling: Show emotions through actions, not dialogue
- Specific details: "weathered chrome" beats "old metal"
- Atmospheric writing: Set mood through environment
- Lean prose: Each word should serve the image
Common Pitfalls to Avoid
- ❌ Vague descriptions: "A person walks" → ✅ "A weathered woman in her 50s trudges through snow"
- ❌ Telling emotions: "She feels sad" → ✅ "Tears streak her dusty cheeks"
- ❌ Camera directions: "CLOSE UP ON" → ✅ "The crack in the glass spreads"
- ❌ Over-dialogue: Short films need visual storytelling
- ❌ Inconsistent character names: Stick to ONE name per character
Additional Resources
Pipeline Integration Guide
- references/pipeline-integration.md
Advanced Techniques
- references/advanced-techniques.md