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.
Scanned 9/9/2026
Install to Claude Code
npx -y skills add badgids/Story-Film-Skills --skill story-architecture --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Story Architecture?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/badgids-story-architecture)More formats (shields.io, HTML) on the badges page.
---
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.
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!
Ultra-compressed communication mode. Cuts token usage ~75% by speaking like caveman while keeping full technical accuracy. Supports intensity levels: lite, full (default), ultra, wenyan-lite, wenyan-full, wenyan-ultra. Use when user says "caveman mode", "talk like caveman", "use caveman", "less tokens", "be brief", or invokes /caveman. Also auto-triggers when token efficiency is requested.
Adversarial multi-agent planning skill. Self-orchestrates 5 hostile category members (unspecified-low, unspecified-high, deep, ultrabrain, artistry) via team-mode for ruthless cross-critique debate, distills only the defensible insights, then MANDATORILY hands the distilled insight bundle to the `plan` agent for executable plan formalization. Use when planning needs maximum rigor and surfacing of weak assumptions, blind spots, and over-engineering. Triggers: 'hyperplan', 'hpp', '/hyperplan', ...
Routes multi-tool workflows through MCP servers for large datasets and pipelines. Use when Bash tool overhead is limiting throughput on data-heavy tasks.
Recovers prior coding-agent session context by running `catchup <agent> --since-compact`, which extracts a clean summary of a previous Codex, Claude Code, Antigravity, OpenCode, or Pi Agent session. Use when the user says "catch up", "what did the last session do", "get me up to speed", "I switched agents", or asks to recover/summarize a previous session before continuing. Do NOT use for the current conversation, git history, or any non-agent log.
A comprehensive mathematical reasoning skill for AI assistants — handles arithmetic to research-level problems with rigorous step-by-step reasoning, systematic verification, and transparent uncertainty handling