Stats
Actions
Tags
Help us improve
Share bugs, ideas, or general feedback.
From skills-for-humanity
Diagnoses and repairs flat, purposeless scenes using the want/obstacle/outcome framework. Every scene must change the story's state.
npx claudepluginhub human-avatar/skills-for-humanityHow this skill is triggered — by the user, by Claude, or both
Slash command
/skills-for-humanity:s4h-writing-scene-constructionThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Every scene is a mini-story. It needs a want, an obstacle, and an outcome. Without these three elements, it is not a scene — it is a passage of time. The reader experiences the difference viscerally, even if they can't name it: a scene without these elements reads as static, as nothing happening, as the story marking time.
Diagnoses plot structure failures using the five-beat dramatic framework (inciting incident, first turning point, midpoint, dark night, climax). Use when a story loses momentum, drags in the middle, or feels structurally loose.
Writes a screenplay scene in industry-standard format (slugline, action lines, dialogue) from a scene brief and character notes, ready to drop into a draft.
Share bugs, ideas, or general feedback.
Every scene is a mini-story. It needs a want, an obstacle, and an outcome. Without these three elements, it is not a scene — it is a passage of time. The reader experiences the difference viscerally, even if they can't name it: a scene without these elements reads as static, as nothing happening, as the story marking time.
The outcome is the most frequently broken element. Every scene must end in a different state than it began. The outcome must be one of four types: yes-but (protagonist gets what they want but at a cost or complication), no-and (denied, and things are worse), no-but (denied, but something else is gained), or yes-and (achieved, and something else follows). Any scene that ends with an unmodified yes or no is a scene that hasn't done its work.
The second most common failure: scenes that serve one function when they need to serve two. A scene that only reveals character, only provides information, or only advances plot is vulnerable to cutting. The best scenes do two or three things at once — and the obligation to do multiple things simultaneously is what generates the density that makes scenes feel necessary.
Step 1: Scene Goal What does the POV character want in this scene? Not what they want in the story — what they want right now, from this specific situation. Be concrete: "to convince Marcus to lend her the money," not "to solve her financial problems." If the goal can't be stated specifically, the scene has no engine.
Framing check: Confirm the specific scene before continuing. State what you've identified — the scene's POV character, their immediate want, and the narrative moment it occupies — in one sentence, then use AskUserQuestion:
Step 2: Obstacle What prevents the character from getting it? The obstacle should be active and specific — a person with their own opposing goal, a circumstance that makes the goal impossible, or an internal conflict that prevents the character from acting. Weak obstacles are vague ("things are difficult") or absent (the character just gets what they want).
Step 3: Outcome Type Identify the outcome type:
Flag any scene ending in an unmodified yes ("they agreed and left") or unmodified no ("he refused and she walked out"). These scenes have not changed the story's state in a way that matters.
Step 4: Sensory Grounding Which senses are present in the scene? Which is doing the most work? What's missing? Scenes that live only in dialogue and action are often missing the physical world — temperature, smell, sound, texture — that makes the reader inhabit the space rather than read about it. Note: sensory detail should not be decoration; it should carry meaning (the smell of the room is connected to what the room means).
Step 5: Subtext What is NOT being said, but is present in the scene? Great scenes carry at least two conversations — the surface exchange and the subterranean one. If the characters are saying exactly what they mean, the scene has no subtext and reads as flat. Identify what each character is not saying and why.
Step 6: Scene Function What does this scene do? Mark all that apply:
If the scene serves only one function, it is at risk. Consider whether it can be combined with adjacent scenes or rewritten to serve a second function.
Before proceeding, use the AskUserQuestion tool. State your interpretation of the situation in 1–2 sentences — what is being analyzed and what the core question is — then ask:
Proceed based on their selection. If the user reframes, incorporate the correction before running any analysis.
Goal: [POV character's specific want in this scene]
Obstacle: [What prevents it — active and specific]
Outcome Type: [yes-and / yes-but / no-but / no-and / FLAGGED: unmodified]
Sensory Inventory: [Senses present / which dominates / what's missing / whether detail carries meaning]
Subtext Present: [What is not said + why / FLAGGED: no subtext]
Scene Function: [Revelation / Escalation / Character / Transition — mark all present, flag if only one]
Verdict: Keep / Cut / Combine / Rewrite
Specific Recommendation: [Concrete intervention — what to add, remove, shift, or rewrite]
/s4h-writing-dialogue for subtext-specific repair./s4h-writing-prose-elevation — the scene's architecture is right but the prose isn't delivering it./s4h-writing-dialogue for scene-specific dialogue repair./s4h-writing-inconsistency-audit for scene-level continuity errors (character knows something they shouldn't, objects change location, etc.)./s4h-writing-plot-structure when diagnosing whether a scene is failing because the structural beat it belongs to is itself failing.After delivering this output, use AskUserQuestion to offer the next move:
/s4h-writing-dialogue — Add dialogue to the scene/s4h-writing-prose-elevation — Elevate the scene's prose/s4h-aesthetic-coherence-check — Check the scene coheres with the whole