Imported from badgids/Story-Film-Skills (skills/story-film-suite/bundle/skills/story-architecture/SKILL.md). Install upstream with npx skills add badgids/Story-Film-Skills --skill story-architecture. Copyright stays with the author (Apache-2.0).

Story Architecture

Name: story-architecture
Author: badgids

Workflow

Read ../../references/CORE_CONTRACT.md, STORY_CRAFT.md, STYLE_RULES.md, and the brief.
Write 01_story/logline.md with one primary logline plus a one-sentence dramatic question.
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.
Choose structure because it fits the story. Do not label acts, beats, themes, or engines merely to fill a formula.
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.

# after Install: the listing is in your workspace's routing pool - a plan picks it for its slot curl -s -X POST https://api.opensmartroute.ai/api/v1/route -H 'Authorization: Bearer $OSR_API_KEY' -H 'Content-Type: application/json' -d '{"text": "...", "plan": true}'

{ "ocm": "1", "id": "badgids-story-film-skills-story-architecture", "kind": "skill", "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.", "publisher": "badgids", "version": "1.0.0", "capabilities": { "domains": [ "creative" ], "tags": [ "skill-md", "github" ], "languages": [ "en" ] }, "quality_prior": 0.6, "examples": [ "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." ], "primary": false, "metadata": { "source": { "provider": "github", "repository": "https://github.com/badgids/Story-Film-Skills", "path": "skills/story-film-suite/bundle/skills/story-architecture/SKILL.md", "ref": "5ec9daf3950a987424a879ab5fef583b013afa8a", "url": "https://github.com/badgids/Story-Film-Skills/blob/5ec9daf3950a987424a879ab5fef583b013afa8a/skills/story-film-suite/bundle/skills/story-architecture/SKILL.md", "key": "badgids/Story-Film-Skills/skills/story-film-suite/bundle/skills/story-architecture/SKILL.md" }, "license": "Apache-2.0" }, "instructions": "# Story Architecture\n\n## Workflow\n\n1. Read `../../references/CORE_CONTRACT.md`, `STORY_CRAFT.md`, `STYLE_RULES.md`, and the brief.\n2. Write `01_story/logline.md` with one primary logline plus a one-sentence dramatic question.\n3. 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 reco", "cost": { "context_tokens": 253 } }

story-architecture

About

Story Architecture

Workflow

Done

Use it

Manifest

Reviews