From crucible-suite
Generates chapter-by-chapter outlines from Crucible story structure planning documents.
How this skill is triggered — by the user, by Claude, or both
Slash command
/crucible-suite:crucible-outlinerThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Transform Crucible planning documents into detailed chapter-by-chapter outlines with proper narrative craft.
Transform Crucible planning documents into detailed chapter-by-chapter outlines with proper narrative craft.
Read these references based on the outlining phase:
references/beat-to-chapter-mapping.md — How 36 beats map to chaptersreferences/narrative-craft.md — Foreshadowing, pacing, scene structurereferences/outline-templates.md — Chapter and scene outline formatsCRITICAL: Use the AskUserQuestion tool, NOT plain text A/B/C options.
The user must have completed Crucible planning. Request uploads of:
Phase 1: SETUP → Load planning docs, confirm scope, establish parameters
Phase 2: STRUCTURE → Map beats to chapters, identify act breaks
Phase 3: CHAPTERS → Outline each chapter through questions
Phase 4: CRAFT → Add foreshadowing threads, verify payoffs
Phase 5: COMPILE → Generate final outline documents
Request the Crucible Thesis first:
To begin outlining, I need your Crucible planning documents.
Please upload your **Crucible Thesis** (or paste its contents).
This contains your core elements: burden, fire, constellation, theme, etc.
After receiving, extract and confirm:
Use AskUserQuestion to confirm scope:
{
"questions": [
{
"header": "Book Type",
"question": "Which book are we outlining?",
"options": [
{"label": "Standalone novel", "description": "A single, complete novel"},
{"label": "Book in series", "description": "Part of a larger series (specify which book)"},
{"label": "Series overview", "description": "Full series overview first, then individual books"}
],
"multiSelect": false
},
{
"header": "Chapter Count",
"question": "What is your target chapter count?",
"options": [
{"label": "Standard (20-25)", "description": "Typical novel length"},
{"label": "Compact (15-20)", "description": "Tighter, faster-paced structure"},
{"label": "Extended (25-35)", "description": "More room for subplot development"},
{"label": "Story dictates", "description": "Let the narrative determine chapter count"}
],
"multiSelect": false
}
]
}
python scripts/init_outline.py "./outline-project" "Title" "Book X of Y"
Using references/beat-to-chapter-mapping.md, establish the chapter skeleton:
For standard 20-25 chapter book:
| Movement | Beats | Chapters | % of Book |
|---|---|---|---|
| I. Ignition | 1-6 | 1-5 | 10% |
| II. First Tempering | 7-14 | 6-10 | 20% |
| III. Scattering | 15-22 | 11-16 | 25% |
| IV. Brightest Burning | 23-28 | 17-21 | 25% |
| V. Final Forging | 29-34 | 22-24 | 15% |
| Coda | 35-36 | 25 | 5% |
Present the proposed structure:
**Proposed Chapter Structure for [Title]**
MOVEMENT I — IGNITION (Chapters 1-5)
• Ch 1: [Beat 1 - The Unlit Forge]
• Ch 2: [Beats 2-3 - Dual Arrival + First Spark]
• Ch 3: [Beat 4 - The Burden Chosen]
• Ch 4: [Beat 5 - First Constellation]
• Ch 5: [Beat 6 - IGNITION FORGE POINT]
[Continue for all movements...]
Use AskUserQuestion to confirm:
```json
{
"questions": [
{
"header": "Structure",
"question": "Does this chapter structure work for your story?",
"options": [
{"label": "Approve structure", "description": "Proceed with this chapter layout"},
{"label": "Adjust count", "description": "Modify the number of chapters"},
{"label": "Discuss sections", "description": "Talk through specific movements or chapters"}
],
"multiSelect": false
}
]
}
Based on which movement is being outlined, request relevant docs:
For each chapter, work through:
**CHAPTER [X]: [Working Title]**
Beat(s): [Which Crucible beats this covers]
Strand Focus: [Quest/Fire/Constellation]
POV: [If dual/multiple POV]
**1. OPENING**
Where does the reader enter this chapter?
A) Immediate action/tension
B) Character reflection/interiority
C) World/setting establishment
D) Dialogue/interaction
E) Time skip from previous chapter
F) Other (describe)
**2. CORE SCENES**
What must happen in this chapter? (Select all that apply)
A) [Beat-specific requirement from Crucible]
B) [Beat-specific requirement]
C) Foreshadowing plant for [future payoff]
D) Character development moment
E) World-building revelation
F) Other (describe)
**3. CHAPTER TURN**
How does this chapter end?
A) Cliffhanger — immediate tension
B) Revelation — new information changes everything
C) Decision point — character commits to action
D) Emotional beat — feeling resonates into next chapter
E) Question raised — reader needs to know what's next
F) Other (describe)
For each scene within a chapter:
**SCENE [X.Y]**
**Goal:** What must this scene accomplish?
**Conflict:** What opposes the goal?
**Disaster/Turn:** How does it shift?
**Characters present:**
**Location:**
**Tone/Mood:**
**Key dialogue/moments:**
**Plants/Payoffs:**
- Sets up: [future scene]
- Pays off: [previous setup]
python scripts/save_outline.py "./outline-project"
After completing chapter skeletons, add craft elements:
Using references/narrative-craft.md, track:
**FORESHADOWING TRACKER**
Thread: [Description]
├── Plant: Chapter [X], Scene [Y] — [How it's planted]
├── Water: Chapter [X] — [How it's reinforced]
└── Payoff: Chapter [X], Scene [Y] — [How it resolves]
Required threads for Crucible stories:
Check chapter-by-chapter:
Each Forge Point chapter must have:
python scripts/compile_outline.py "./outline-project"
Creates:
outline/
├── master-outline.md # Full book outline
├── chapter-summaries.md # Quick reference
├── scene-breakdown.md # Detailed scene list
├── foreshadowing-tracker.md # Plant/payoff tracking
├── character-threads.md # Per-character arcs
└── by-chapter/
├── ch01-outline.md
├── ch02-outline.md
└── ...
✅ **Outline Complete: [Title]**
📄 [View Master Outline](computer:///path/outline/master-outline.md)
📄 [View Chapter Summaries](computer:///path/outline/chapter-summaries.md)
📄 [View Scene Breakdown](computer:///path/outline/scene-breakdown.md)
📄 [View Foreshadowing Tracker](computer:///path/outline/foreshadowing-tracker.md)
Use AskUserQuestion for next steps:
```json
{
"questions": [
{
"header": "Next Steps",
"question": "What would you like to do next?",
"options": [
{"label": "Review chapters", "description": "Review and adjust specific chapters"},
{"label": "Outline next book", "description": "Continue to next book in series"},
{"label": "Begin drafting", "description": "Start writing prose from this outline"},
{"label": "Add scene detail", "description": "Expand detail on specific scenes"}
],
"multiSelect": false
}
]
}
For series, outline books in order. Track:
Cross-Book Elements:
Before outlining Book 2+, request:
Provides UI/UX resources: 50+ styles, color palettes, font pairings, guidelines, charts for web/mobile across React, Next.js, Vue, Svelte, Tailwind, React Native, Flutter. Aids planning, building, reviewing interfaces.
Fetches up-to-date documentation from Context7 for libraries and frameworks like React, Next.js, Prisma. Use for setup questions, API references, and code examples.
npx claudepluginhub pasteurmonga/the-crucible-writing-system-for-claude