Design or repair a story core: logline, dramatic question, protagonist goal, opposition, stakes, change, ending logic, and a causal architecture appropriate to the requested form.
Installs into .claude/skills of the current project.
Sponsors
SSkills DirectorySkills Directory
Know which skills are safe — weekly.
SSkills DirectorySkills Directory
Is that skill safe to install?
Are you the author of Story Architecture?
Add the live security badge to your README. It updates with every re-scan.
[](https://www.skillsdirectory.com/skills/badgids-story-architecture)
---
name: story-architecture
description: "Design or repair a story core: logline, dramatic question, protagonist goal, opposition, stakes, change, ending logic, and a causal architecture appropriate to the requested form."
disable-model-invocation: true
author: Alan Guice (Badgids)
license: Apache-2.0
---
# Story Architecture
## Workflow
1. Read `../../references/CORE_CONTRACT.md`, `STORY_CRAFT.md`, `STYLE_RULES.md`, and the brief.
2. Write `01_story/logline.md` with one primary logline plus a one-sentence dramatic question.
3. Write `01_story/story_bible.md` with protagonist goal, opposition, stakes, internal pressure, central relationships, causal spine, escalation strategy, climax choice, ending state, and intentionally unresolved material. Add a thematic tension when the project has a recurring human/value conflict, and recurring narrative engines only when the story genuinely reuses recognizable scene or sequence shapes.
4. Choose structure because it fits the story. Do not label acts, beats, themes, or engines merely to fill a formula.
5. Test causality from setup through climax. Replace "and then" chains with consequence where possible.
## Done
The climax resolves the same dramatic problem the beginning establishes, and every major movement has a causal reason to follow the previous one.