forsonny/the-crucible-writing-system-for-claude/crucible-outliner
Claude Code and agent skill by forsonny/the-crucible-writing-system-for-claude
- community
Checking that the SKILL.md file is still in the repository.
Chapter-by-chapter outline generator for stories planned with the Crucible Structure. Use when a user has completed Crucible planning documents (thesis, strand maps, forge points, etc.) and wants to create detailed chapter outlines. Triggers on requests like "outline my book," "create chapter outline," "outline Book 1," "turn my Crucible plan into chapters," or when user has Crucible planning docs and wants to start writing. Works for single books or multi-book series.
Install
npx vskill@latest install forsonny/the-crucible-writing-system-for-claude/crucible-outlinerSKILL.md
Crucible Outliner
Transform Crucible planning documents into detailed chapter-by-chapter outlines with proper narrative craft.
Before Starting
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 formats
Questioning Rules
- ALWAYS use AskUserQuestion tool for all user questions (provides interactive UI)
- Max 4 options per question (tool limit) + "Other" is automatic
- Max 4 questions per AskUserQuestion call
- Reference user's story elements by name (characters, places, etc.)
- Save state after each chapter outline
CRITICAL: Use the AskUserQuestion tool, NOT plain text A/B/C options.
Required Inputs
The user must have completed Crucible planning. Request uploads of:
- Crucible Thesis (required first) — Core elements: burden, fire, constellation, theme
- Strand Maps (required) — Quest, Fire, Constellation arcs
- Forge Point Blueprints (required) — The convergence crises
- Constellation Bible (as needed) — Character details
- Mercy Ledger (as needed) — Setup/payoff tracking
- World Forge (as needed) — Setting details
Workflow
Phase 1: Setup
Load Planning Documents
Request the Crucible Thesis first:
After receiving, extract and confirm:
- Theme
- Burden type
- Fire nature
- Core bond
- Dark mirror connection
- Surrender moment
- Blade's purpose
Confirm Scope
Use AskUserQuestion to confirm scope:
Initialize Project
Phase 2: Structure
Map Beats to Chapters
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:
{ "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 } ] }
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)
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"
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]
python scripts/compile_outline.py "./outline-project"
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 📄 View Chapter Summaries 📄 View Scene Breakdown 📄 View Foreshadowing Tracker
Use AskUserQuestion for next steps:
Multi-Book Series Handling
For series, outline books in order. Track:
Cross-Book Elements:
- Mercy plants in Book X → Payoffs in Book Y
- Character arcs spanning multiple books
- Foreshadowing threads that span books
- Series-level pacing (which book is darkest, etc.)
Before outlining Book 2+, request:
- Previous book outline(s)
- Updated character states
- Unresolved threads list
Questioning Principles
- Max 2-3 questions per message — Don't overwhelm
- Always offer "Other" option — User knows their story
- Reference their documents — Use their character names, places, elements
- Explain the "why" — Brief context for why this choice matters
- Save state frequently — After each chapter or major decision
Security
- Security scanPassed, 100 of 100Pattern checks on the skill's files.
- Model reviewPassed
Quality evaluation
- Task evaluationNot runNo evaluation yet. Run one in Skill Studio.
Source
- SKILL.md in the repositoryCheckingskills/crucible-outliner/SKILL.md
Popularity
- Repository stars
- 45
- Repository forks
- 14
- 7-day trend score
- 19
Stars and forks are for the whole GitHub repository, not this skill alone. Refreshed 24 Mar 2026, 7 months ago.
Works with
Any agent vskill installs to: 56 targets in all. These 39 have a page on this site.
- Claude Code
- Cursor
- GitHub Copilot
- Windsurf
- Codex
- Gemini CLI
- Cline
- Amp
- Roo Code
- Goose
- Continue
- Kilo Code
- Junie
- Trae
- OpenHands
- Qwen Code
- AI Agent
- Tabnine Chat
- Sourcegraph Cody
- Amazon Q
- Firebase Genkit
- Sweep
- Devin
- Phind
- Mentat
- Claude Desktop
- Aider
- GPT Pilot
- Plandex
- bolt.new
- v0
- Replit Agent
- Anse
- TypingMind
- BetterChatGPT
- LibreChat
- Warp AI
- Pieces
- Fig AI
Embed badge
[](https://verified-skill.com/skills/forsonny/the-crucible-writing-system-for-claude/crucible-outliner)