Detalle del Skill

writers-room

Directly supports screenplay planning and major creative rewrites.

CoincidenciaDirectaRevisado para redactores
Fuentebybren-llc/story-systems-templateFuente externa
Instalaciones reportadas50Solo señal de popularidad

Revisar antes de usar

La revisión automática comprueba relevancia, no seguridad ni respaldo. Lee las instrucciones de la fuente antes de usar este Skill.

Vista previa guardada

SKILL.md

Este extracto es una copia guardada durante la revisión. La fuente externa contiene la versión completa y actual.

---
name: writers-room
wtfbId: wtfb:writers-room
description: |
  This skill convenes a 6-seat collaborative pre-production session — Story Architect,
  Story Analyst, Dialogue Writer, Scene Writer, Standards Reviewer, and Research Specialist
  pitch their creative visions before writing begins. Optionally convenes the seats across
  MULTIPLE models/providers (Claude + self-hosted vLLM + cloud) for genuine diversity.

  Use when: starting a new screenplay, planning major rewrites,
  reimagining existing material, or seeking diverse expert perspectives.
---

# Writer's Room Skill

## Purpose

A collaborative pre-production workflow where multiple specialized agents pitch their creative visions before any writing begins. This creates diverse perspectives, healthy creative tension, and a synthesized approach that draws from the best ideas.

## When to Use

- Before starting a new screenplay or major rewrite
- When reimagining existing material
- When the creative direction is uncertain
- When you want multiple expert perspectives before committing

## Participants

The Writer's Room convenes 6 specialized agents, each with a distinct role:

### Story Architect
**Focus:** Structure and form
- Alternative three-act structures
- Non-linear possibilities
- Scene sequence options
- Climax variations
- Pacing strategies

### Story Analyst
**Focus:** Character and meaning
- Character arc potential
- Thematic depth opportunities
- Aristotle's Six Components evaluation
- What the story is *really* about
- Theophrastus archetype analysis

### Dialogue Writer
**Focus:** Voice and tone
- Character voice distinctions
- Comedic/dramatic rhythm
- Language approach (profanity, dialect, period)
- Signature lines and moments
- Subtext opportunities

### Scene Writer
**Focus:** Visual storytelling
- Key visual setpieces
- Physical comedy/action beats
- Power dynamics per scene
- Compression opportunities
- "Show don't tell" moments

### Standards Reviewer
**Focus:** Quality and originality
- What makes each proposed element A-grade?
- Weak points to avoid
- Cliche identification
- Fresh vs. derivative analysis
- Genre boundary awareness

### Research Specialist
**Focus:** Authenticity and grounding
- Setting accuracy requirements
- Technical/professional accuracy
- Historical or cultural considerations
- Real-world logic checks
- Reference material needs

## Process

### Step 1: Brief the Room
Provide all participants with:
- The core premise/logline
- Any existing material (V1 script, source material, notes)
- Target tone and audience
- Constraints (runtime, budget considerations, rating)
- What's "sacred" vs. open for reimagining

### Step 2: Individual Pitches
Each agent prepares their perspective:
- What excites them about the material
- Their proposed approach
- Specific recommendations
- Potential concerns or warnings

### Step 3: Synthesis
Combine the best elements from all pitches into:
- A unified creative direction
- Key scenes that must exist
- Tone and voice guidelines
- What's explicitly off-limits
- The "North Star" for the project

## Multi-Model Council (opt-in)

By default every seat is played by its routed Claude model (see `.claude/model-routing.md`) —
"diverse perspectives" from diverse *prompts*. The council upgrade lets the room convene diverse
*minds*: some seats on Claude, some on a self-hosted vLLM model, some on another cloud. This is
additive — the default behavior is unchanged.

### Modes

- **`solo` (default):** all six seats = their routed Claude models. No registry or endpoints
  needed. This is exactly the classic Writer's Room.
- **`diverse`:** seats spread across providers, plus optional **guest seats** on rostered
  non-Claude models (e.g. a local Qwen/Llama wildcard, a Gemini seat).
- **`custom`:** an explicit seat→model roster provided at invocation.

### How the council runs

The **Session Manager** conducts:

1. **Read the roster.** `node scripts/model-consult.js list` (or the `list_models` MCP tool if the
   
Leer la fuente completa en GitHub (abre una página externa)
Contexto

Trabajo relacionado