Individual skill
s4h-writing-scene-construction
Diagnoses and repairs individual scenes using the want/obstacle/outcome framework. Every scene must change the story's state. Use when a scene feels flat, static, or purposeless. Triggers: 'this scene isn't working', 'scene construction', 'scene feels flat', 'scene review', 'fix this scene', 'the scene doesn't do anything', 'should I cut this scene'.
skills/s4h-writing-scene-construction/SKILL.md
Source commit a30df8b67698ccb03ef5e35d68c2eddc5321ad3f
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- Yes
- Repository scan complete
- No
- Skill scan complete
- Yes
- Observed behavior
- Instructions only
- Last checked
- Nov 11, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 241
- Repository last updated
- Jul 15, 2026
- License
- MIT
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- claude-code Repository topic
- claude-code-plugin Repository topic
- cognitive-frameworks Repository topic
- creativity Repository topic
- decision-making Repository topic
- ethics Repository topic
- mental-models Repository topic
- problem-solving Repository topic
- reasoning Repository topic
- systems-thinking Repository topic
- writing Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
SKILL.mdcore · 7,490 bytes
Read excerpt
# Writing: Scene Construction
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.
---
## Your Process
**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.