forsonny/the-crucible-writing-system-for-claude/crucible-writer
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.
First-draft writing assistant for Crucible-planned novels. Use when author has completed planning (crucible-planner) and outlining (crucible-outliner) and wants to write the actual prose. Handles scene-by-scene drafting, style matching, continuity tracking, and hallucination prevention. Triggers on "write my novel," "draft chapter X," "start writing from my outline," "help me write my book," or when user has Crucible outline and wants prose output. Works with any Crucible-planned story.
Install
npx vskill@latest install forsonny/the-crucible-writing-system-for-claude/crucible-writerSKILL.md
Crucible Writer
Transform Crucible outlines into first-draft prose while maintaining style consistency, plot fidelity, and narrative quality.
Critical Principles
Context Window is Limited. Never try to hold the entire novel in context. Load only what's needed for the current scene. Save constantly.
The Outline is Law. Never invent plot points, characters, or events not in the outline. If something seems missing, ASK the author—don't improvise.
Style is Sacred. Capture the author's voice early. Maintain it relentlessly. When in doubt, match the sample.
Save Everything. After every scene, update the story bible and save the draft. Progress must survive session breaks.
Before Starting
Read these references based on the writing phase:
references/context-management.md— Critical: Managing limited AI contextreferences/writing-process.md— Scene-by-scene drafting approachreferences/style-capture.md— Learning and maintaining author voicereferences/anti-hallucination.md— Verification protocolsreferences/prose-craft.md— Genre conventions and techniques
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 every scene and chapter
CRITICAL: Use the AskUserQuestion tool, NOT plain text A/B/C options.
Required Inputs
Before writing can begin, gather:
- Complete Chapter Outline (required) — The crucible-outliner output
- Crucible Summary Card (required) — Quick reference for theme, characters
- Style Sample (required) — 2,000+ words of author's existing prose OR detailed style preferences
- Constellation Bible (as needed) — Character details
- World Forge (as needed) — Setting details
Workflow Overview
Phase 1: Project Setup
Initialize the Draft Project
Request Essential Documents
Confirm Writing Parameters
Present the extracted parameters, then use AskUserQuestion:
Phase 2: Style Capture
CRITICAL: Read references/style-capture.md before this phase.
Analyze the Style Sample
Extract and document:
Confirm Style Profile
Present the style profile and sample, then use AskUserQuestion:
Phase 3: Chapter Writing
Pre-Chapter Context Loading
For each chapter, load ONLY:
- Current chapter outline (from the full outline)
- Previous chapter summary (from story bible—NOT full text)
- Active character states (from story bible)
- Relevant foreshadowing (plants that pay off OR are planted this chapter)
- Style profile (from Phase 2)
Do NOT load:
- Full text of previous chapters (too large)
- Chapters not adjacent to current
- Planning documents not directly relevant
Scene-by-Scene Writing
Each chapter contains multiple scenes. Write ONE SCENE AT A TIME:
After each scene:
- Show word count
- Ask if author wants to review before continuing
- Option to revise before moving on
Scene Writing Protocol
For each scene, follow this sequence:
- State what you're writing (goal, conflict, turn)
- Write the prose (matching style profile)
- Verify against outline (all required elements present?)
- Note any plants/payoffs executed
- Update running word count
Chapter Completion
After all scenes in a chapter:
Use AskUserQuestion for chapter approval:
Update Story Bible
After each chapter, update the story bible to track progress and continuity:
For complete command reference, see references/story-bible-commands.md.
Key commands:
--chapter X— Update chapter summary and timeline--location— Track new locations--relationship— Track character relationships--mercy-act/--mercy-refused— Track Mercy Engine--status X— Check chapter status--report— Generate continuity report
Bi-Chapter Review System
CRITICAL: Every 2 chapters, a comprehensive review MUST be triggered to catch issues early.
For complete review workflow, see references/bi-chapter-review.md.
Quick Reference
- Mark chapter complete:
python scripts/save_draft.py "./draft-project" --complete-chapter X summary.txt - Review triggers when
chapters_complete - last_review_at_chapter >= 2 - Run 5 agents in parallel: voice-checker, continuity-checker, outline-checker, timeline-checker, prose-checker
- Address critical issues before continuing
Phase 4: Compile Manuscript
After all chapters complete:
Creates:
Hallucination Prevention Protocol
CRITICAL: Read references/anti-hallucination.md for full protocol.
The Three Laws
- If it's not in the outline, don't write it. Missing a scene? Ask the author.
- If you're unsure about a detail, ask. Don't guess character names, places, rules.
- If you need to invent minor details, flag them. Mark with [INVENTED] for author review.
Verification Checkpoints
Before writing each scene:
- Do I have the scene outline loaded?
- Do I know the required elements?
- Are there unknowns I need to ask about?
After writing each scene:
- Did I include all required elements?
- Did I invent anything significant?
- Does this match what came before?
Before saving each chapter:
- Full outline verification
- Continuity check against story bible
- Flag any [INVENTED] details for author
Continuing a Paused Session
When returning to a draft:
Use AskUserQuestion:
Handling Author Feedback
When author requests changes:
Scene-level revision:
Style adjustment:
Plot deviation (author wants to change outline):
When the author wants to deviate from the outline, use AskUserQuestion:
Word Count Management
This is the start of the file. Read the full SKILL.md on GitHub.
Security
- Security scanPassed, 95 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-writer/SKILL.md
Popularity
- Repository stars
- 41
- Repository forks
- 11
- 7-day trend score
- 19
Stars and forks are for the whole GitHub repository, not this skill alone. Refreshed 16 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-writer)