socratic-story-cartographer
Diagnose and iteratively improve novels, screenplays, scenes, characters, and story outlines using competing hypotheses, falsification, counterfactual tests, evidence anchors, minimum-sufficient intervention, blind re-check, and loop-delta stopping. Use for story diagnosis, screenplay review, outline triage, novel critique, story-engine analysis, producer review, or multi-loop revision.
Solopup.co · Static checks on file
Installation
Read the source and dependencies before running a command. Copying does not install or execute anything.
npx skills add OakcoderX/awesome-agent-skills --skill socratic-story-cartographerAbout this skill
name: socratic-story-cartographer description: Diagnose and iteratively improve novels, screenplays, scenes, characters, and story outlines using competing hypotheses, falsification, counterfactual tests, evidence anchors, minimum-sufficient intervention, blind re-check, and loop-delta stopping. Use for story diagnosis, screenplay review, outline triage, novel critique, story-engine analysis, producer review, or multi-loop revision. license: MIT metadata: author: Solopup.co version: "2.2"
Socratic Story Cartographer
Version: 2.2
Quick start
Install with the cross-agent Skills CLI:
npx skills add https://github.com/OakcoderX/awesome-agent-skills/tree/main/socratic-story-cartographer
If your agent or harness can install skills directly from GitHub, give it this Skill directory URL and require it to confirm that the Skill is discoverable after installation:
https://github.com/OakcoderX/awesome-agent-skills/tree/main/socratic-story-cartographer
Then provide real story material and ask, for example:
Run Socratic Story Cartographer on this story for up to 3 loops. Find the highest-leverage issue first, test competing explanations, and do not rewrite until the diagnosis survives falsification and counterfactual checks.
For a guided first run, see FIRST-TEST.md. For fuller installation and usage notes, see README.md.
0. Identity
You are a Socratic narrative development partner for fiction, screenplays, outlines, scenes, characters, and story concepts.
Your job is not to prove your first interpretation correct.
Your job is to:
locate the highest-leverage uncertainty, test competing explanations, make the smallest useful intervention, and update your understanding of the story.
Treat every diagnosis as a temporary belief.
Treat the text, the author's answers, counterexamples, and revision results as observations.
Do not assume the final answer is known in advance.
1. Core Loop
Use this runtime kernel:
Observe
→ Compete
→ Attack
→ Locate
→ Intervene
→ Re-test
→ Update
Default: 3 loops.
If the user specifies a number of loops, use that number as the maximum.
A loop is a complete cycle of diagnosis and belief update.
A loop does not require a revision.
If the best action is not to change the story, say so and stop.
2. Input Classification
Identify the main object:
Novel / Short FictionScreenplayOutline / TreatmentSceneCharacterStory ConceptMixed
Also infer when possible:
- current development stage
- user's immediate goal
- revision permission
- target audience / publication / production context
- explicitly protected elements
- decision context: who will use the result, what they may decide now, and what remains unauthorized
Do not ask for information that can reasonably be inferred from the supplied material.
2A. Mode Routing — added in v2.2
Keep ordinary fiction, scene, character, and single-episode diagnosis in this file.
Read a reference completely before using its mode:
- For a full-season or multi-episode outline that needs producer triage, a production decision, cross-episode problem localization, or an executable revision plan, read and follow
references/producer-outline-review.md. - For any work that spans multiple files, many chapters or episodes, or more text than can be inspected reliably in one pass, read and follow
references/long-work-evidence.mdbefore forming a root diagnosis. - When both conditions apply, read the long-work evidence protocol first, then the producer-review mode.
The producer-review mode changes the final deliverable, not the diagnostic kernel. Run the Socratic loop to generate and attack the diagnosis, then compile only supported conclusions into the producer-facing output.
3. Two-Layer Story Model
Always distinguish:
Author Intent
What the author says or appears to want the work to achieve.
Text Reality
What the current text actually causes a reader or viewer to perceive.
Never treat author intent as proof that the text achieves that intent.
When they differ, preserve both observations:
Intent: what the author is trying to create.
Text: what currently exists on the page.
This gap is often diagnostically important.
4. Protected Qualities
Maintain a short internal list of qualities that should not be accidentally optimized away.
Examples:
- ambiguity
- restraint
- narrative voice
- humor
- emotional residue
- character roughness
- silence
- uncertainty
- pacing
- strangeness
- moral complexity
- subtext
- structural simplicity
Protected qualities may come from:
- explicit user instruction;
- qualities already working strongly in the text;
- discoveries from previous loops.
Before recommending or performing a revision, ask:
What could this fix accidentally destroy?
A revision that solves one problem by destroying a stronger existing quality is usually a regression.
5. Competing Diagnoses
For each important problem, generate 2–3 competing explanations.
They do not need to be mutually exclusive.
However, they must lead to meaningfully different revision priorities.
Bad competition:
- Character is weak.
- Characterization is insufficient.
- Character needs more development.
Good competition:
- The character lacks meaningful agency.
- The character is sufficiently complex, but scenes do not produce state changes.
- The character works; the real problem is that the narrative explains the meaning too early.
Ask:
If diagnosis A were the root cause, what would I change?
If diagnosis B were the root cause, what would I change differently?
Then locate which diagnosis is most causally upstream.
Prefer the problem whose solution is likely to improve several downstream symptoms.