WriteStory
🚨 MANDATORY: Voice Notification (REQUIRED BEFORE ANY ACTION)
You MUST send this notification BEFORE doing anything else when this skill is invoked.
-
Send voice notification:
curl -s -X POST http://localhost:8888/notify \ -H "Content-Type: application/json" \ -d '{"message": "Running the WORKFLOWNAME workflow in the WriteStory skill to ACTION"}' \ > /dev/null 2>&1 & -
Output text notification:
Running the **WorkflowName** workflow in the **WriteStory** skill to ACTION...
This is not optional. Execute this curl command immediately upon skill invocation.
WriteStory
Layered fiction writing system that constructs stories across seven simultaneous narrative dimensions, powered by Will Storr's The Science of Storytelling and Mark Forsyth's The Elements of Eloquence.
Customization
Before executing, check for user customizations at:
~/.claude/skills/PAI/USER/SKILLCUSTOMIZATIONS/WriteStory/
If this directory exists, load and apply:
PREFERENCES.md- User preferences, default genre, aesthetic, voice- Additional files specific to the skill
Workflow Routing
Route to the appropriate workflow based on the request.
When executing a workflow, output this notification directly:
Running the **WorkflowName** workflow in the **WriteStory** skill to ACTION...
| Workflow | Trigger | File |
|---|---|---|
| Interview | "interview me", "extract my story ideas", "help me plan a story" | Workflows/Interview.md |
| BuildBible | "build story bible", "create story plan", "map the story" | Workflows/BuildBible.md |
| Explore | "explore ideas", "brainstorm", "creative exploration", "what if" | Workflows/Explore.md |
| WriteChapter | "write chapter", "write scene", "write prose", "draft" | Workflows/WriteChapter.md |
| Revise | "revise", "edit", "improve", "polish", "rewrite" | Workflows/Revise.md |
The Seven Story Layers
Every story in this system is constructed across seven simultaneous layers:
- Meaning — Theme, philosophical argument, lesson
- Character Change — Sacred flaw -> transformation arc (Storr)
- Plot — Cause-and-effect chain of events
- Mystery — Information management (reader knows vs. doesn't)
- World — Setting, politics, physical environment, rules
- Relationships — How key bonds evolve and pressure characters
- Prose — Rhetorical figures, voice, aesthetic, style
Core References
| Reference | File | Purpose |
|---|---|---|
| Layer Architecture | StoryLayers.md |
Seven-layer system definition |
| Storr Framework | StorrFramework.md |
Character change, sacred flaw, mystery |
| Rhetorical Figures | RhetoricalFigures.md |
Comprehensive rhetorical figures catalogue |
| Anti-Cliche System | AntiCliche.md |
Freshness enforcement, banned patterns |
| Story Structures | StoryStructures.md |
Save the Cat, Dramatica, Story Grid |
| Aesthetic Profiles | AestheticProfiles.md |
Genre and style configuration |
| Critic Profiles | Critics.md |
Multi-pass review system for prose refinement |
Quick Reference
- Theoretical Foundation: Storr (character science) + Forsyth (rhetoric) + classical rhetoric
- Story Bible: PRD-based plan mapping all 7 layers start-to-finish
- Scale: Short story (100s of ISC) to multi-book series (10,000s of ISC)
- Anti-Cliche: Built-in freshness system bans generic AI patterns
- Aesthetic: Configurable per project (Adams, Tolkien, sparse sci-fi, etc.)
Examples
Example 1: Starting from scratch
User: "I have an idea for a fantasy novel about an elven princess raised by orcs"
→ Invokes Interview workflow
→ Extracts character concepts, world details, themes
→ Maps ideas across seven story layers
→ Produces structured input for BuildBible
Example 2: Building the full story plan
User: "Build the story bible for my novel"
→ Invokes BuildBible workflow
→ Creates Story Bible PRD with all layers mapped start-to-finish
→ Identifies milestones, character transformations, mystery reveals
→ Outputs comprehensive layered narrative plan
Example 3: Writing actual prose
User: "Write chapter 3 based on the story bible"
→ Invokes WriteChapter workflow
→ Reads Story Bible PRD for chapter milestones across all layers
→ Deploys rhetorical figures for memorable dialogue
→ Produces fresh, anti-cliche prose in configured aesthetic
More from danielmiessler/personal_ai_infrastructure
osint
Structured OSINT investigations — people lookup, company intel, investment due diligence, entity/threat intel, domain recon, organization research using public sources with ethical authorization framework. USE WHEN OSINT, due diligence, background check, research person, company intel, investigate, company lookup, domain lookup, entity lookup, organization lookup, threat intel, discover OSINT sources.
259firstprinciples
Physics-based reasoning framework (Musk/Elon methodology) that deconstructs problems to irreducible fundamental truths rather than reasoning by analogy. Three-step structure: DECONSTRUCT (break to constituent parts and actual values), CHALLENGE (classify every element as hard constraint / soft constraint / unvalidated assumption — only physics is truly immutable), RECONSTRUCT (build optimal solution from fundamentals alone, ignoring inherited form). Outputs: constituent-parts breakdown, constraint classification table, and reconstructed solution with key insight. Three workflows: Deconstruct.md, Challenge.md, Reconstruct.md. Integrates with RedTeam (attack assumptions before deploying adversarial agents), Security (decompose threat model), Architecture (challenge design constraints), and Pentesters (decompose assumed security boundaries). Other skills invoke via: Challenge on all stated constraints → classify as hard/soft/assumption. Cross-domain synthesis: solutions from unrelated fields often apply once the fundamental truths are exposed. NOT FOR incident investigation and causal chains (use RootCauseAnalysis). NOT FOR structural feedback loops (use SystemsThinking). USE WHEN first principles, fundamental truths, challenge assumptions, is this a real constraint, rebuild from scratch, what are we actually paying for, what is this really made of, start over, physics first, question everything, reasoning by analogy, is this really necessary.
160documents
Read, write, convert, and analyze documents — routes to PDF, DOCX, XLSX, PPTX sub-skills for creation, editing, extraction, and format conversion. USE WHEN document, process file, create document, convert format, extract text, PDF, DOCX, XLSX, PPTX, Word, Excel, spreadsheet, PowerPoint, presentation, slides, consulting report, large PDF, merge PDF, fill form, tracked changes, redlining.
114council
Multi-agent collaborative debate that produces visible round-by-round transcripts with genuine intellectual friction. All council members are custom-composed via ComposeAgent (Agents skill) with domain expertise, unique voice, and personality tailored to the specific topic — never built-in generic types. ComposeAgent invoked as: bun run ~/.claude/skills/Agents/Tools/ComposeAgent.ts. Two workflows: DEBATE (3 rounds, full transcript + synthesis, parallel execution within rounds, 40-90 seconds total) and QUICK (1 round, fast perspective check). Context files: CouncilMembers.md (agent composition instructions), RoundStructure.md (three-round structure and timing), OutputFormat.md (transcript format templates). Agents are designed per debate topic to create real disagreement; 4-6 well-composed agents outperform 12 generic ones. Council is collaborative-adversarial (debate to find best path); for pure adversarial attack on an idea, use RedTeam instead. NOT FOR parallel task execution across agents (use Delegation skill). USE WHEN council, debate, multiple perspectives, weigh options, deliberate, get different views, multi-agent discussion, what would experts say, is there consensus, pros and cons from multiple angles.
112privateinvestigator
Ethical people-finding using 15 parallel research agents (45 search threads) across public records, social media, reverse lookups. Public data only, no pretexting. USE WHEN find person, locate, reconnect, people search, skip trace, reverse lookup, social media search, public records search, verify identity.
112redteam
Military-grade adversarial analysis that deploys 32 parallel expert agents (engineers, architects, pentesters, interns) to stress-test ideas, strategies, and plans — not systems or infrastructure. Two workflows: ParallelAnalysis (5-phase: decompose into 24 atomic claims → 32-agent parallel attack → synthesis → steelman → counter-argument, each 8 points) and AdversarialValidation (competing proposals synthesized into best solution). Context files: Philosophy.md (core principles, success criteria, agent types), Integration.md (how to combine with FirstPrinciples, Council, and other skills; output format). Targets arguments, not network vulnerabilities. Findings ranked by severity; goal is to strengthen, not destroy — weaknesses delivered with remediation paths. Collaborates with FirstPrinciples (decompose assumptions before attacking) and Council (Council debates to find paths; RedTeam attacks whatever survives). Also invoked internally by Ideate (TEST phase) and WorldThreatModel (horizon stress-testing). NOT FOR AI instruction set auditing (use BitterPillEngineering). NOT FOR network/system vulnerability testing (use a security assessment skill). USE WHEN red team, attack idea, counterarguments, critique, stress test, devil's advocate, find weaknesses, break this, poke holes, what could go wrong, strongest objection, adversarial validation, battle of bots.
112