narrative-develop
Skill2 starsChanged 3 months agoMITView on GitHub
Develop narrative ideas into story concepts, story-relevant characters and worlds, outlines, beats, and scene plans. Use for premise development, concept alternatives, character motivation and arcs, world constraints, story structure, beat sheets, scene cards, and structural refinement before or alongside prose or screenplay drafting.
In this repository27 other files it gives its agents.
- acquire-codebase-knowledgeSkill
- ai-qa-reviewSkill
- ci-cd-and-automationSkill
- code-review-and-qualitySkill
- code-simplificationSkill
- contract-testingSkill
- documentation-and-adrsSkill
- github-actions-hardeningSkill
- github-issuesSkill
- incremental-implementationSkill
- nodeSkill
- release-readinessSkill
- risk-based-testingSkill
- security-and-hardeningSkill
- skill-creatorSkill
- skill-optimizerSkill
- systematic-debuggingSkill
- test-strategySkill
- typescript-magicianSkill
- unit-testingSkill
- verification-before-completionSkill
- writing-skillsSkill
- narrative-continuitySkill
- narrative-evaluateSkill
- narrative-pack-createSkill
- narrative-reviseSkill
- narrative-writeSkill
The file
We split this skill into the rules it gives an agent
7 rules. About 0 are common, 6 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈6
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 23
Prefer low-resolution concept/outline/beat/scene-card work before full prose when it can answer the question.
- Distinctive: line 27
Treat beats as meaningful changes with causes and consequences, not simply small scenes.
- Distinctive: line 30
No structural framework is mandatory.
- Distinctive: line 34
When refining, state or infer:
- Distinctive: line 45
If prose reveals a better upstream decision, surface the discovery and update the relevant planning artifact deliberately.
- Distinctive: line 55
Do not create visual character designs, storyboards, cinematography, model-provider integrations, graph/vector infrastructure, or unrelated …
- Distinctive: line 57
Read the local references when the task requires deeper guidance.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Narrative Develop
Develop the story at the lowest useful narrative resolution before spending effort on higher-resolution writing.
Operating sequence
- Identify the smallest relevant target: brief, concept, character, world, outline, beat sheet, or scene card.
- Determine workflow state:
draft,refine, orfinal. - Determine decision status where useful:
candidate,selected,approved,rejected, orsuperseded. - Load only relevant upstream constraints.
- Explore alternatives only where meaningful uncertainty remains.
- Preserve selected and approved decisions.
- Evaluate at the current narrative resolution before escalating.
Core rules
- Prefer low-resolution concept/outline/beat/scene-card work before full prose when it can answer the question.
- Candidate alternatives must differ in story logic, not merely wording.
- Character material should affect story behaviour; do not default to encyclopaedic biographies.
- World material should support or constrain the story; do not create lore for completeness.
- Treat beats as meaningful changes with causes and consequences, not simply small scenes.
- A scene card records why the scene exists: entry state, objective, conflict, turn, exit state, information, and continuity needs.
- Branch at the smallest creative unit containing the uncertainty.
- No structural framework is mandatory.
Refinement
When refining, state or infer:
preserve
changeChange only the target deficiency and update downstream planning only where actually affected.
Discovery writing
If prose reveals a better upstream decision, surface the discovery and update the relevant planning artifact deliberately. Do not let written narrative silently diverge from the story model.
Evaluation
- Draft: useful enough to continue; no catastrophic contradiction; respects hard constraints.
- Refine: requested change worked; approved decisions survived; no major regression.
- Final: planning artifact is coherent and ready for its downstream consumer.
Boundaries
Do not create visual character designs, storyboards, cinematography, model-provider integrations, graph/vector infrastructure, or unrelated world encyclopaedias.
Read the local references when the task requires deeper guidance.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.