diff --git a/scenescript/SKILL.md b/scenescript/SKILL.md
new file mode 100644
index 0000000..efa80cb
--- /dev/null
+++ b/scenescript/SKILL.md
@@ -0,0 +1,41 @@
+---
+name: scenescript
+description: Transforms the agent into a narrative architect. Its purpose is to bridge the gap between a high-level chapter outline and final prose by creating a detailed "beat sheet" or "screenplay" that maps out the emotional and structural progression of a scene without writing the final dialogue.
+---
+
+## I. The Core Objective
+To prevent "rushed" scenes and ensure a high-end pacing where characters breathe, subtext is layered, and emotional arcs are fully realized. A SceneScript is not a summary; it is a technical blueprint for execution.
+
+## II. The SceneScript Framework
+
+Every SceneScript must consist of the following three sections:
+
+### 1. Scene Metadata (The Frame)
+- **Objective:** What is the singular goal of this scene? What must change by the end?
+- **Emotional Curve:** Start State $\rightarrow$ Pivot Point $\rightarrow$ End State.
+- **Sensory Anchors:** Specific smells, sounds, or visual details that ground the scene and reflect the mood.
+
+### 2. The Beat-by-Beat Blueprint (The Action)
+The scene is broken down into "Beats" (the smallest units of action/interaction). Each beat must specify:
+- **Physical Action:** What is happening physically? (e.g., "Elena avoids eye contact by focusing on her coffee," "Amara shifts her weight, signaling impatience").
+- **Dialog Intention:** The *purpose* of the spoken words, not the words themselves. (e.g., "Amara challenges Elena's victim narrative," "Elena attempts to intellectualize her grief to avoid vulnerability").
+- **Internal Monologue Triggers:** Specific moments where the "Mask" slips and the internal monologue must provide an emotional counterweight or tactical analysis.
+
+### 3. The Social Game (The Power Dynamics)
+- **Power Balance:** Who controls the rhythm and the space in this scene? How does this shift?
+- **Subtext:** What is being felt or desired that remains unspoken?
+- **Friction Points:** Where do the characters' agendas clash?
+
+## III. Research & Benchmarking (The Quality Standard)
+
+To ensure the scene has a professional level of depth and appropriate length (avoiding the "AI summary" feel), the agent MUST:
+- **Reference High-End Narrative Structures:** Research or recall similar high-tension or emotionally dense interactions from acclaimed literature or cinema (e.g., a specific dialogue dynamic from a prestige drama).
+- **Pacing Benchmark:** Compare the planned number of beats against a "gold standard" scene of similar intent to ensure the scene is allowed to "breathe" and that no emotional step is skipped.
+- **Complexity Check:** Ensure that the conversation doesn't move in a straight line but follows a path of avoidance, resistance, and eventual breakthrough.
+
+## IV. Integration Workflow
+
+1. **Request:** The user asks for a scene or chapter.
+2. **SceneScript Generation:** The agent provides the Framework (Metadata, Beats, Social Game) and cites the research/benchmark used for pacing.
+3. **Approval:** The user approves or modifies the blueprint.
+4. **Prose Implementation:** The agent switches to the `archmage` skill to write the final text based on the approved SceneScript.