# Cowork-Z Micro-Drama Pack Builder + Script Generator Agent

## Overview

This document guides you through creating a professional Cowork-Z Workspace Pack for micro-drama and short-form script writing. The pack demonstrates Cowork-Z's multi-file context capabilities, supervised file writes, and HTML artifact generation.

### What is Micro-Drama?

Micro-drama is a short-form video script format (typically 60-180 seconds per episode) characterized by:

- Rapid plot development
- Strong emotional hooks in every scene
- Episode-based storytelling with cliffhangers
- Limited cast (2-5 main characters)
- Mobile-first, vertical video format

---

## Part A — Create Cowork-Z Workspace Pack

### Step 1: Create Directory Structure

Create the following directory at the project root:

```
workspace-packs/packs/micro-drama-script-studio-pack/
├── PACK_INFO.md          # Pack metadata and description
├── START_HERE.md         # Step-by-step user instructions
├── PROMPTS.md            # Five copy/paste prompts for Cowork-Z
├── EXPECTED_OUTPUTS.md   # Quality criteria and validation
├── inputs/               # Curated source materials
│   ├── STYLE_GUIDE.md    # Tone, pacing, structure guidelines
│   ├── SCRIPT_FORMAT.md  # Script template and conventions
│   ├── CHARACTER_SHEETS.md
│   ├── EXAMPLE_EPISODES/
│   │   ├── episode_001.md
│   │   └── episode_002.md
│   └── TOPIC_GUIDES/
├── outputs/              # Generated content (gitkeep only)
│   └── .gitkeep
├── .packignore           # Optional exclusions log
└── SAMPLE_OUTPUTS/       # Pre-generated examples (optional)
```

### Step 2: Required Files Specification

#### PACK_INFO.md

```markdown
# Micro-Drama Script Studio Pack

## What This Pack Demonstrates

This Cowork-Z Workspace Pack showcases several key capabilities:

1. **Multi-File Context**: Reads multiple reference files (style guide, examples, character sheets) simultaneously
2. **Supervised Writes**: Generates structured outputs with explicit file paths and approval flow
3. **Artifact Generation**: Creates HTML documents with rich formatting and interactive elements
4. **Iterative Workflow**: Follows a logical progression from premise → outline → draft → polish

## Pack Details

- **Estimated Completion Time**: 10-15 minutes
- **Complexity Level**: Intermediate
- **Outputs Produced**:
  - Episode script (Markdown)
  - Writer's Room Dashboard (HTML)
  - Episode beats document (Markdown)
  - Cast sheet (Markdown)

## Use Cases

- Learning micro-drama script structure
- Rapid prototyping of new drama concepts
- Generating content for short-form video platforms
- Demonstrating Cowork-Z's capabilities to stakeholders

## Prerequisites

- Basic understanding of scriptwriting conventions
- Familiarity with markdown formatting
- Access to Cowork-Z workspace environment

## Safety & Licensing

All content generated by this pack is:

- **Original**: Synthesized from your prompts, no third-party text
- **Safe**: No personal data, secrets, or copyrighted material
- **Usable**: Clear license for any purpose (public domain)

---

## Technical Notes

### File Reading Order

When Cowork-Z processes this pack, files are read in this priority:

1. STYLE_GUIDE.md (defines all constraints)
2. SCRIPT_FORMAT.md (defines structure)
3. CHARACTER_SHEETS.md (reference for dialogue)
4. EXAMPLE_EPISODES/\*.md (format and tone examples)

### Output Naming Convention

Generated files follow this pattern:

- `outputs/episode_XXX.md` - Episode scripts
- `outputs/writers_room_dashboard_YYYYMMDD.html` - Dashboard artifacts
- `outputs/episode_beats_XXX.md` - Outline documents

### Character Name Convention

All character names should follow the pattern: `NAME_INITIAL` (e.g., `A:`, `B:`, `M:`, `W:`)
```

#### START_HERE.md

```markdown
# Getting Started - Micro-Drama Script Studio

## Quick Start (5 Minutes)

### Step 1: Open Cowork-Z

Launch the Cowork-Z application and ensure you're logged into your workspace.

### Step 2: Select Workspace Pack

1. Click "Select Workspace" or "Open Folder"
2. Navigate to `workspace-packs/packs/micro-drama-script-studio-pack/`
3. Confirm selection

### Step 3: Begin Prompt 1 - Workspace Scan

Copy and paste Prompt #1 from PROMPTS.md into the chat:
```

Scan the inputs/ directory and create a summary document that:

1. Lists all available reference materials
2. Extracts tone guidelines and style constraints
3. Identifies script format requirements
4. Notes any special conventions or banned content
   Save your summary to outputs/workspace_scan.md

```
5. Review the files Cowork-Z wants to read
6. Approve the read operation

### Step 4: Proceed Through the Workflow
Follow prompts sequentially:
- **Prompt 2**: Develop 3 premise options, choose one
- **Prompt 3**: Create detailed episode beats/outline
- **Prompt 4**: Write the full episode script
- **Prompt 5**: Generate HTML dashboard artifact

### Step 5: Review Generated Outputs
1. Open `outputs/` folder in your file explorer
2. Open `episode_001.md` to review the script
3. Open `writers_room_dashboard.html` in a browser
4. Check that all sections render correctly

---

## Approval Workflow Details

### Read Approvals
When Cowork-Z requests to read files:
1. Review the list of files
2. Confirm they match expected inputs
3. Click "Approve" to proceed

### Write Approvals
When Cowork-Z requests to write:
1. Check the file path (should be in `outputs/`)
2. Verify the format matches your expectations
3. Click "Approve" to confirm

### Multiple Approvals
Some prompts require multiple approvals. Review each request individually.

---

## Troubleshooting

| Issue | Solution |
|-------|----------|
| Can't find pack folder | Ensure you're in the `workspace-packs/packs/` directory |
| Files not showing | Click refresh in Cowork-Z or restart the application |
| Prompt not working | Ensure you're using the exact prompt text from PROMPTS.md |
| HTML not rendering | Open in a modern browser (Chrome, Firefox, Safari, Edge) |
| Character names wrong | Check CHARACTER_SHEETS.md for correct format |

---

## Tips for Best Results

1. **Be Patient**: Each prompt builds on the previous output
2. **Review Early**: Check intermediate outputs before proceeding
3. **Iterate**: You can re-run prompts with modified instructions
4. **Save Work**: Export important outputs to your local machine
5. **Provide Feedback**: Use Cowork-Z's feedback features to improve results

---

## Expected Output Locations

All generated content will appear in:
```

workspace-packs/packs/micro-drama-script-studio-pack/outputs/

```

Typical outputs include:
- `workspace_scan.md` (from Prompt 1)
- `premise_selection.md` (from Prompt 2)
- `episode_beats_001.md` (from Prompt 3)
- `episode_001.md` (from Prompt 4)
- `writers_room_dashboard_*.html` (from Prompt 5)

---

## Next Steps

After completing the basic workflow:
1. Try alternative premises from Prompt 2
2. Generate episode variants (episode_001_alt.md)
3. Create a multi-episode arc
4. Adapt the format for different genres
```

#### PROMPTS.md

```markdown
# Cowork-Z Prompts - Micro-Drama Script Studio

Copy and paste these prompts sequentially into Cowork-Z. Each prompt builds on the previous outputs.

---

## Prompt 1: Workspace Scan & Constraint Extraction
```

You are a micro-drama script analyst. Your task is to scan all files in the inputs/ directory and produce a comprehensive summary.

Read ALL files in inputs/ including:

- STYLE_GUIDE.md
- SCRIPT_FORMAT.md
- CHARACTER_SHEETS.md
- All files in EXAMPLE_EPISODES/
- All files in TOPIC_GUIDES/

Create a summary document (outputs/workspace_scan.md) that includes:

## Available Reference Materials

- List each file with a 1-sentence description of its purpose

## Tone & Style Guidelines

- Primary emotional tone(s)
- Target episode length
- Pacing characteristics
- Voice/style requirements

## Script Format Requirements

- Scene heading format
- Character name conventions
- Dialogue formatting
- Action line style
- Any special notations

## Content Constraints

- Topics to avoid
- Content sensitivities
- Platform requirements

## Example Analysis

- What makes the example episodes effective?
- Key patterns in dialogue and structure
- Common phrases or tropes

Save your summary to outputs/workspace_scan.md and explain your reasoning before writing.

```

---

## Prompt 2: Writer's Room - Premise Development

```

You are a micro-drama showrunner. Using the style guidelines and constraints from inputs/, develop three distinct episode premises.

For EACH premise, provide:

## Premise Option [1/2/3]

**Logline**: One sentence hook (max 20 words)

**Genre**: [e.g., Romance, Thriller, Comedy, Drama, Sci-Fi]

**Setting**: Where does this story take place?

**Core Conflict**: What is the central tension or problem?

**Character Pairing**:

- Character A: [Brief description and motivation]
- Character B: [Brief description and motivation]

**Episode Hook**: What creates the initial intrigue (first 10 seconds)?

**Cliffhanger**: What leaves viewers wanting the next episode?

**Episode Structure**:

- Scene 1 (0-30s): [Setup]
- Scene 2 (30-60s): [Confrontation/Complication]
- Scene 3 (60-90s): [Revelation/Twist]
- Scene 4 (90-120s): [Cliffhanger]

**Tone**: [e.g., Tense, Romantic, Humorous, Melancholic]

**Tropes**: List 2-3 genre tropes used

---

After presenting all three options, recommend ONE option and explain why it best fits the style guidelines. Ask me to choose an option, or proceed with the recommendation if I approve.

Save the premises document to outputs/premises_options.md

```

---

## Prompt 3: Episode Beats & Outline

```

Using the selected premise [INSERT PREMISE NUMBER], create a detailed episode beat sheet.

## Episode Overview

- **Working Title**: [Catchy 3-5 word title]
- **Episode Number**: 001
- **Target Runtime**: [60-180 seconds]
- **Total Scenes**: [3-5 scenes]
- **Characters**: List all characters with brief descriptions

## Scene-by-Scene Beats

### Scene 1: [Title]

- **Duration**: 0-30s
- **Location**: [Setting]
- **Characters Present**: [Who appears]
- **Purpose**: [What this scene accomplishes]
- **Visual Hook**: [Eye-catching visual element]
- **Dialogue Start**: [Opening line suggestion]

### Scene 2: [Title]

- **Duration**: 30-60s
- **Location**: [Setting]
- **Characters Present**: [Who appears]
- **Purpose**: [What this scene accomplishes]
- **Key Moment**: [The scene's highlight]
- **Dialogue Start**: [Opening line suggestion]

[Continue for all scenes...]

### Final Scene: [Title]

- **Duration**: 90-120s or 120-150s
- **Location**: [Setting]
- **Characters Present**: [Who appears]
- **Purpose**: [Set up episode end and cliffhanger]
- **Cliffhanger Element**: [What creates the hook for next episode]

## Pacing Notes

- Rhythm of dialogue vs. action
- Where to accelerate
- Where to pause for impact

## Dialogue Guidelines

- Speech patterns for each character
- Key lines to hit
- Phrases to avoid

## Arc Notes

- How this episode fits the larger story
- Character development moments
- Setup for future episodes

Save to outputs/episode_beats_001.md

```

---

## Prompt 4: Script Draft Generation

```

Write a complete micro-drama episode script based on the beats outline in outputs/episode_beats_001.md.

## Formatting Requirements

Follow the script format from inputs/SCRIPT_FORMAT.md exactly. Use the character naming convention (e.g., A:, B:, M:) consistently.

## Script Structure

### HEADER

```
Episode: 001
Title: [Episode Title]
Runtime: [XX:XX]
Genre: [Genre]
Characters: [List]
```

### SCENES

Format each scene with:

- Scene heading in CAPS
- Brief action lines (present tense, visual)
- Character names in CAPS followed by dialogue
- [beat] notations for pauses
- Parentheticals sparingly for context

### DIALOGUE NOTES

- Keep dialogue punchy and short
- Show emotion through action, not just words
- Each character should have a distinct voice
- Avoid on-the-nose exposition

### RUNTIME CHECK

- Aim for target runtime
- Mark estimated timestamps for each scene
- Ensure cliffhanger lands in final 15 seconds

## Quality Standards

- Every scene advances plot or character
- Dialogue reveals character and advances conflict
- Visual storytelling in action lines
- Clear emotional arc within episode
- Strong cliffhanger that demands a follow-up

## Output Format

Save to: outputs/episode_001.md

Before writing, explain your approach to:

- How you'll handle the opening hook
- The emotional throughline
- How you'll make the cliffhanger effective

Write the script after I approve your approach.

```

---

## Prompt 5: HTML Writer's Room Dashboard

```

Create a comprehensive HTML dashboard artifact that summarizes the entire episode development process.

## Dashboard Sections Required

### 1. Episode Header

- Episode number and title
- Genre and runtime
- Creation date
- Version number

### 2. Premise Card

- Logline (prominently displayed)
- Genre classification
- Core conflict summary
- Tone indicators

### 3. Cast Sheet

- Character list with:
  - Name and role
  - Brief description
  - Personality traits
  - Character arc notes

### 4. Episode Beats Dashboard

- Visual scene breakdown (cards or timeline)
- Each scene with:
  - Scene number
  - Location
  - Duration
  - Key action point
  - Dialogue highlight

### 5. Arc Tracking

- This episode's role in larger story
- Character development markers
- Foreshadowing elements
- Callbacks to earlier episodes

### 6. Production Checklist

- [ ] Script complete
- [ ] Dialogue recorded
- [ ] Locations scouted
- [ ] Visual elements planned
- [ ] Cliffhanger approved
- [ ] CTA for next episode

### 7. Quick Reference

- Key dialogue snippets
- Important visual beats
- Emotional peaks

## Styling Requirements

- Clean, professional design
- Use CSS Grid or Flexbox for layout
- Mobile-responsive
- Print-friendly
- Consistent color scheme
- Readable typography

## Technical Requirements

- Single self-contained HTML file (no external dependencies)
- All CSS inline or in <style> block
- No JavaScript required (or inline only)
- Valid HTML5
- Works offline

Save to: outputs/writers_room_dashboard.html

Before generating, describe your layout approach and color scheme.

```

---

## Quick Prompt Reference

| # | Prompt | Output | Time |
|---|--------|--------|------|
| 1 | Workspace Scan | workspace_scan.md | 2 min |
| 2 | Premise Development | premises_options.md | 3 min |
| 3 | Episode Beats | episode_beats_001.md | 3 min |
| 4 | Script Draft | episode_001.md | 5 min |
| 5 | HTML Dashboard | writers_room_dashboard.html | 3 min |

**Total estimated time**: 15-20 minutes
```

#### EXPECTED_OUTPUTS.md

```markdown
# Expected Outputs - Quality Criteria

This document defines what a successful run of the Micro-Drama Script Studio pack produces and how to validate quality.

---

## Output Files Checklist

### Required Outputs

| File                                  | Status | Quality Check                       |
| ------------------------------------- | ------ | ----------------------------------- |
| `outputs/workspace_scan.md`           | ☐      | Contains all sections from Prompt 1 |
| `outputs/premises_options.md`         | ☐      | 3 distinct premises with all fields |
| `outputs/episode_beats_001.md`        | ☐      | Complete scene breakdown            |
| `outputs/episode_001.md`              | ☐      | Full script in correct format       |
| `outputs/writers_room_dashboard.html` | ☐      | Valid HTML, all sections present    |

### Optional Outputs

| File                         | When Generated          |
| ---------------------------- | ----------------------- |
| `outputs/episode_001_alt.md` | If generating variant   |
| `outputs/episode_002.md`     | If extending series     |
| `outputs/cast_sheet.md`      | If requested separately |

---

## Quality Criteria by Output

### workspace_scan.md

- [ ] Lists ALL files from inputs/
- [ ] Accurately describes tone and style
- [ ] Correctly identifies script format rules
- [ ] Notes all content constraints
- [ ] Provides useful example analysis

**Red Flags**:

- Missing files from inputs/
- Misidentified format requirements
- Contradictory style notes

---

### premises_options.md

- [ ] Three distinct premises (different genres/themes)
- [ ] Each premise has all required fields filled
- [ ] Loglines are under 20 words
- [ ] Cliffhangers are compelling and specific
- [ ] Structure breakdown shows proper timing
- [ ] Recommendation is justified

**Red Flags**:

- Duplicate or too-similar premises
- Missing required fields
- Unrealistic runtime estimates
- Weak or unclear cliffhangers

---

### episode_beats_001.md

- [ ] Working title is catchy and relevant
- [ ] Scene count matches genre expectations (3-5)
- [ ] Each scene has timing, location, purpose
- [ ] Cliffhanger clearly identified
- [ ] Arc notes show larger story awareness
- [ ] Dialogue guidelines are specific

**Red Flags**:

- Scenes too long/short for runtime
- Unclear scene purposes
- Missing or weak cliffhanger
- No arc consideration

---

### episode_001.md

#### Format Validation

- [ ] Proper header with all metadata
- [ ] Scene headings in correct format (CAPS)
- [ ] Character names in correct format (NAME:)
- [ ] Action lines present tense, visual
- [ ] Dialogue formatting consistent throughout

#### Content Validation

- [ ] Opens with strong visual/dialogue hook (first 10 seconds)
- [ ] Every scene has clear purpose
- [ ] Dialogue is punchy and character-distinct
- [ ] Conflict is clear and escalates
- [ ] Episode ends with cliffhanger
- [ ] Runtime is reasonable (60-180 seconds)

#### Style Validation

- [ ] Matches tone from STYLE_GUIDE.md
- [ ] Follows pacing guidelines
- [ ] Respects content constraints
- [ ] Demonstrates genre conventions

**Red Flags**:

- Wrong format entirely
- Dialogue too long or exposition-heavy
- No clear conflict
- Missing or weak opening/closing
- Inconsistent character names

---

### writers_room_dashboard.html

#### Technical Validation

- [ ] File opens in browser without errors
- [ ] All CSS loads correctly
- [ ] No broken links or missing resources
- [ ] Responsive design works on mobile
- [ ] All sections are visible and readable

#### Content Validation

- [ ] Episode header complete
- [ ] Premise card accurate
- [ ] Cast sheet has all characters
- [ ] Scene breakdown matches beats document
- [ ] Checklist is actionable
- [ ] Quick reference section useful

#### Design Validation

- [ ] Clean, professional appearance
- [ ] Good visual hierarchy
- [ ] Appropriate use of color
- [ ] Readable typography
- [ ] Consistent spacing and alignment

**Red Flags**:

- Doesn't open in browser
- Missing sections
- Broken layout
- Hard to read
- Doesn't match source documents

---

## Tone Validation Checklist

Across all outputs, check for:

- [ ] Consistent tone throughout
- [ ] Appropriate emotional beats
- [ ] Genre conventions respected
- [ ] Target audience considered
- [ ] Platform requirements met (short-form, mobile)

---

## Constraint Compliance

Verify that outputs:

- [ ] Avoid all topics in "banned content" list
- [ ] Follow character conventions from inputs/
- [ ] Respect any platform-specific rules
- [ ] Contain no real names/places (unless template)
- [ ] Are original and not derivative

---

## How to Validate HTML Dashboard

### Browser Testing

1. Open file in Chrome, Firefox, Safari, Edge
2. Check console for errors (F12 → Console)
3. Test responsiveness (resize browser window)
4. Verify all links work
5. Print to PDF to test print styles

### Manual Checklist

- [ ] Title displays correctly
- [ ] All cards/sections visible
- [ ] Checklist items can be mentally checked
- [ ] Cast information accurate
- ] Scene breakdown clear

---

## Common Issues & Fixes

| Issue          | Likely Cause                 | Fix                                      |
| -------------- | ---------------------------- | ---------------------------------------- |
| Format wrong   | Didn't read SCRIPT_FORMAT.md | Re-run Prompt 1, then Prompt 4           |
| Weak premise   | Premise too generic          | Re-run Prompt 2 with more specific genre |
| No cliffhanger | Outline missed it            | Re-run Prompt 3 focusing on ending       |
| HTML broken    | Missing closing tags         | Re-run Prompt 5                          |
| Tone off       | Style guide ignored          | Re-run from Prompt 1                     |

---

## Approvals Checklist

Before considering the pack run complete:

- [ ] Read approvals granted for all inputs files
- [ ] Write approval granted for each output file
- [ ] All outputs saved to correct paths
- [ ] HTML dashboard opens successfully
- [ ] Script format validated
- [ ] Content constraints respected
- [ ] Quality criteria met

---

## Reporting Results

If outputs don't meet quality criteria:

1. Note which specific criteria failed
2. Identify which prompt likely needs re-running
3. Consider modifying the prompt with more specific instructions
4. Document any edge cases or unusual requirements
```

#### STYLE_GUIDE.md (in inputs/)

```markdown
# Micro-Drama Style Guide

## Tone & Voice

### Primary Tonal Categories

| Tone          | Characteristics                   | Best For                  |
| ------------- | --------------------------------- | ------------------------- |
| **Emotional** | Melancholic, tender, heartwarming | Romance, family drama     |
| **Tense**     | Suspenseful, urgent, gripping     | Thriller, mystery         |
| **Uplifting** | Hopeful, warm, satisfying         | Comedy, success stories   |
| **Dramatic**  | Intense, pivotal moments          | Conflict-heavy narratives |

### Tone Rules

- Maintain ONE primary tone per episode
- Secondary tones can support (e.g., tense → hopeful resolution)
- Avoid tonal whiplash within single episode
- Match tone to platform and audience expectations

---

## Pacing Guidelines

### Episode Length Targets

| Format       | Duration | Scenes | Words (approx.) |
| ------------ | -------- | ------ | --------------- |
| **Short**    | 60-90s   | 3      | 150-250         |
| **Standard** | 90-120s  | 4      | 250-350         |
| **Extended** | 120-180s | 4-5    | 350-500         |

### Pacing Principles

1. **Hook by 5 seconds**: Visual or dialogue hook must grab attention
2. **Escalate every scene**: Each scene should increase tension/stakes
3. **Pause strategically**: One brief pause per episode for impact
4. **End on high**: Cliffhanger in final 15-20 seconds

### Rhythm Breakdown
```

0-10s: HOOK - Establish premise, grab attention
10-30s: SETUP - Introduce characters, establish conflict
30-60s: DEVELOPMENT - Complications, escalation
60-90s: COMPLICATION - Peak tension, key revelations
90-120s: CLIFFHANGER - End on unresolved tension

```

---

## Episode Structure

### Standard 4-Scene Structure

| Scene | Time | Purpose | Key Element |
|-------|------|---------|-------------|
| 1 | 0-30s | Hook & Setup | Inciting incident |
| 2 | 30-60s | Development | First complication |
| 3 | 60-90s | Escalation | Key revelation/twist |
| 4 | 90-120s | Resolution + Hook | Partial resolution, cliffhanger |

### Scene Requirements

Each scene must have:
- **Visual hook**: Something visually interesting happens
- **Clear purpose**: Advances plot OR develops character
- **Dialogue purpose**: Not just exposition—reveal character/conflict
- **Transition**: Clear to next scene (physical or emotional)

---

## Character Development

### Character Naming

Use initial-based naming for micro-drama:
- Single letter (A, B, C, D)
- Initial + descriptor (MA for "Mother", BO for "Boss")
- Avoid: Full names, gender-specific assumptions

### Character Consistency

- Maintain consistent speech patterns
- Character reactions should match established personality
- Growth should be earned, not sudden
- Keep cast small (2-5 characters per episode)

---

## Dialogue Guidelines

### Do's

- ✓ Use contractions for natural speech
- ✓ Keep lines under 20 words when possible
- ✓ Show emotion through subtext
- ✓ Vary sentence length (short for tension, longer for reflection)
- ✓ Use character-specific verbal quirks

### Don'ts

- ✗ On-the-nose exposition ("As you know, I'm your long-lost brother")
- ✗ Same-syllable repetition (he/she/they)
- ✗ Unnatural explanations for plot convenience
- ✗ More than 3 consecutive dialogue lines without action
- ✗ Breaking character for plot explanation

---

## Banned Content

### Absolute No-Go

- [ ] Graphic violence or gore
- [ ] Sexual content or nudity
- [ ] Hate speech or discrimination
- [ ] Illegal activities promoted
- [ ] Dangerous stunts or behaviors
- [ ] Real people or real brands
- [ ] Medical misinformation
- [ ] Self-harm or suicide encouragement

### Platform Restrictions

- [ ] Varies by platform (TikTok, Reels, Shorts)
- [ ] Check current community guidelines
- [ ] Avoid political content
- [ ] No copyrighted music/lyrics

---

## Formatting Conventions

### Scene Headings

```

INT. LOCATION - TIME

```
Examples:
```

INT. COFFEE SHOP - DAY
EXT. ROOFTOP - NIGHT
INT. OFFICE - MORNING

```

### Character Names

```

CHARACTER:
Dialogue here.

```

### Action Lines

- Present tense
- Visual and specific
- Under 2 lines when possible
- Describe what we SEE, not internal thoughts

### Parentheticals

Use sparingly for:
- Physical actions affecting delivery
- Which character they're speaking to
- Important emotional beats

Example:
```

A:
(holding out hand)
Take it.

```

### [beat] Notation

For significant pauses:
```

[beat] She realizes the truth.

```

---

## Genre Tropes & Conventions

### Romance

- First meeting / Reunion / Misunderstanding
- Secret admirer / Hidden identity
- Love triangle
- Second chance romance

### Thriller

- Hidden camera / Surveillance
- Wrong person / Case of mistaken identity
- Countdown / Time pressure
- Secret revealed

### Comedy

- Awkward situation / Mistaken identity
- Role reversal / Fish out of water
- Overheard conversation
- Perfectly timed interruption

### Drama

- Family conflict / Generational divide
- Sacrifice / Difficult choice
- Reconciliation / Forgiveness
- Life-changing news

---

## Quality Checklist

Before finalizing any episode:

- [ ] Opens with strong hook (within 5 seconds)
- [ ] Every scene has purpose
- [ ] Dialogue is punchy and natural
- [ ] Emotional beats land
- [ ] Pacing feels right
- [ ] Cliffhanger is compelling
- [ ] Matches tone guidelines
- [ ] Follows format conventions
- [ ] No banned content
- [ ] Runtime appropriate for format

---

## Common Mistakes to Avoid

1. **Over-explaining**: Trust the audience to follow visual cues
2. **Slow starts**: Every second counts—get to the conflict
3. **Weak endings**: Cliffhanger must be memorable
4. **Flat characters**: Give everyone a clear want/obstacle
5. **Repeating info**: Don't say what we've already seen
6. **All talk, no action**: Show, don't just tell
7. **Forgetting format**: Scene headings, character names, etc.

---

## Platform-Specific Notes

### TikTok/Reels/Shorts

- Maximum impact in first 3 seconds
- Vertical video friendly descriptions
- Text overlays can supplement dialogue
- Music/sound cues can be referenced

### General Best Practices

- Assume sound ON (dialogue matters)
- Design for mobile viewing
- Consider autoplay context
- Leave room for captions
```

---

## Part B — Generate Example Scripts

### Episode Script Template

```markdown
Episode: 001
Title: [Catchy Title]
Runtime: [MM:SS]
Genre: [Genre]
Characters: A, B, [others]

---

INT. [LOCATION] - [TIME]

[Action lines describing what we see. Present tense, visual, brief.]

A:
[Dialogue - punchy, character-specific, under 20 words]

B:
[Response]

[beat]

A:
[Next line]

---

INT. [LOCATION] - [TIME]

[Scene transition - escalation from previous scene]

[Continue same format through all scenes...]

---

INT. [LOCATION] - [FINAL SCENE]

[Cliffhanger setup - visual or dialogue]

A:
[Final line that creates intrigue]

[END EPISODE - CLIFFHANGER]
```

### Example Episode (episode_001.md)

```markdown
Episode: 001
Title: The Wrong Number
Runtime: 02:00
Genre: Romance/Drama
Characters: A (Young professional), B (Stranger)

---

INT. COFFEE SHOP - MORNING

A sits alone, typing furiously on laptop. Phone buzzes.

A:
(grabbing phone)
Another text from Mom. "Call me back. It's important."

A ignores it. Types more.

---

INT. A'S APARTMENT - NIGHT

A collapses on couch. Phone buzzes again. Different number.

B: (TEXT)
"Sorry, wrong number. But since you're reading—hope your day got better."

A stares at screen. Types a reply.

A: (TEXT)
"It didn't. But this made me smile. Thanks."

---

INT. COFFEE SHOP - ONE WEEK LATER

A sits at same spot. Same laptop. Phone buzzes.

B: (TEXT)
"I keep texting this number by accident. You still there?"

A looks around the coffee shop. No one matching B's implied presence.

A: (TEXT)
"I'm here. But I don't even know who you are."

B: (TEXT)
"Would you like to?"

[beat]

A types. Hesitates. Types again.

A: (TEXT)
"Meet me here tomorrow. 10 AM. I'll be the one who's been answering."

---

INT. COFFEE SHOP - NEXT MORNING

A sits at corner table. Checking phone nervously. Checking door.

DOOR CHIME

A looks up—

SMASH CUT TO BLACK.

A:
(VO)
"Every love story has a beginning. This one started with a wrong number."

TEXT ON SCREEN: "TO BE CONTINUED..."

[END EPISODE - CLIFFHANGER]
```

---

## Part C — Safety & Licensing Documentation

### Safety Statement (for PACK_INFO.md)

```markdown
## Safety & Licensing

### Content Safety

This workspace pack generates original content using your specifications and templates. No third-party copyrighted material is included in outputs.

**What we protect:**

- Your personal data and prompts remain private
- No real names, emails, or identifiers are used
- Generated content is yours to use freely

**What we avoid:**

- No real people, companies, or trademarks
- No copyrighted text, lyrics, or dialogue
- No content that violates platform guidelines
- No harmful, illegal, or dangerous instructions

### Licensing

All outputs generated by this pack are:

- **Original Works**: Created fresh based on your inputs
- **Public Domain**: No copyright restrictions
- **Yours to Use**: Commercial or personal use permitted
- **No Attribution Required**: Though always appreciated

### Third-Party Materials

The inputs/ folder may contain reference materials you provided. These remain under your ownership. The curated versions in this pack have been sanitized for safe distribution.

If you didn't provide source materials:

- All examples are original and created for this pack
- No third-party scripts or text have been copied
- Any "real world" references are generic placeholders

### Distribution

This pack is safe to:

- Share with team members
- Distribute publicly
- Include in training materials
- Use in commercial contexts

---

## Privacy Notes

### What Cowork-Z Sees

- Files in this workspace pack
- Your prompts
- Generated outputs

### What Cowork-Z Doesn't See

- Your personal files outside this pack
- Credentials or API keys
- Private communications

### Best Practices

1. Don't include real contact information
2. Don't use actual company names in examples
3. Don't reference real projects or clients
4. Review outputs before sharing publicly
```

---

## Directory Tree Template

```
micro-drama-script-studio-pack/
├── PACK_INFO.md
├── START_HERE.md
├── PROMPTS.md
├── EXPECTED_OUTPUTS.md
├── inputs/
│   ├── STYLE_GUIDE.md
│   ├── SCRIPT_FORMAT.md
│   ├── CHARACTER_SHEETS.md
│   ├── EXAMPLE_EPISODES/
│   │   ├── episode_001.md
│   │   └── episode_002.md
│   └── TOPIC_GUIDES/
│       ├── romance_tropes.md
│       └── thriller_conventions.md
├── outputs/
│   └── .gitkeep
└── .packignore (optional)
```

---

## Deliverables Summary

### What You Must Provide

1. **Final directory tree** showing all created files
2. **Full contents** of all new Markdown files
3. **Copy log**: Which original files were copied to inputs/ and why
4. **Exclusion notes**: What was removed for safety/privacy

### File Origins

| Input File             | Source  | Reason for Inclusion                    |
| ---------------------- | ------- | --------------------------------------- |
| STYLE_GUIDE.md         | Created | Defines all constraints and style rules |
| SCRIPT_FORMAT.md       | Created | Documents format requirements           |
| CHARACTER_SHEETS.md    | Created | Provides character reference            |
| EXAMPLE_EPISODES/\*.md | Created | Shows format in practice                |

### Excluded Items

| Excluded               | Reason                               |
| ---------------------- | ------------------------------------ |
| Personal notes         | Not relevant to pack users           |
| Draft versions         | Only final curated versions included |
| Third-party references | Sanitized or replaced                |
| Real names/emails      | Privacy protection                   |

---

## Quality Standards

### Pack Quality

- [ ] All required files present and complete
- [ ] File paths are correct and consistent
- [ ] Markdown formatting is clean and valid
- [ ] Instructions are clear and actionable

### Content Quality

- [ ] Scripts are tight and punchy
- [ ] Dashboard is visually structured
- [ ] Prompts produce expected outputs
- [ ] All constraints are clearly documented

### Documentation Quality

- [ ] START_HERE.md is truly beginner-friendly
- [ ] PROMPTS.md has exact prompt text
- [ ] EXPECTED_OUTPUTS.md has actionable checks
- [ ] PACK_INFO.md explains pack purpose clearly

---

## Implementation Checklist

Before finalizing the pack:

- [ ] Created all required files
- [ ] Verified directory structure matches spec
- [ ] Populated inputs/ with curated materials
- [ ] Wrote STYLE_GUIDE.md with all constraints
- [ ] Created PACK_INFO.md with pack metadata
- [ ] Wrote START_HERE.md with step-by-step instructions
- [ ] Wrote PROMPTS.md with all 5 prompts
- [ ] Wrote EXPECTED_OUTPUTS.md with quality criteria
- [ ] Created outputs/ with .gitkeep
- [ ] Wrote .packignore (if needed)
- [ ] Generated sample episode script
- [ ] Verified all file paths are correct
- [ ] Checked for any personal data or secrets
- [ ] Tested that prompts are copy/paste ready
- [ ] Validated markdown formatting

---

## Final Review Questions

Before delivering the pack:

1. **Is it usable?** Would a new user understand what to do?
2. **Is it safe?** No secrets, no personal data, no copyright issues?
3. **Is it complete?** All required files present?
4. **Is it accurate?** Does it reflect proper script format?
5. **Is it quality?** Would you be proud to share this?

If you answer "yes" to all five, the pack is ready for delivery.
