write
/write
This skill should be used when the user asks to "write chapter X", "write the next chapter", "write prose", "continue the story", "continue from where we left off", "draft the next scene", "write a scene where...", or invokes `/holocron:write`. Spawns the writer agent to produce manuscript prose, with project context loaded.
- Author
- petitchu ↗
- Repository
- holocron ↗
- Licence
- MIT
- Last repository change
- 12.05.2026
Assessment and security
- Files in this package
- 1
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 12.05.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
What it does and when to use it
This skill should be used when the user asks to "write chapter X", "write the next chapter", "write prose", "continue the story", "continue from where we left off", "draft the next scene", "write a scene where...", or invokes `/holocron:write`. Spawns the writer agent to produce manuscript prose, with project context loaded.
Triggers from the description
Arguments
/write [chapter|scene|description]
Original author description
This skill should be used when the user asks to "write chapter X", "write the next chapter", "write prose", "continue the story", "continue from where we left off", "draft the next scene", "write a scene where...", or invokes `/holocron:write`. Spawns the writer agent to produce manuscript prose, with project context loaded.
How it works
- Usage
- How this dispatches
- Reference files the writer should consult
- When to use this vs. other commands
- Failure modes
SKILL.md preview
--- name: write description: This skill should be used when the user asks to "write chapter X", "write the next chapter", "write prose", "continue the story", "continue from where we left off", "draft the next scene", "write a scene where...", or invokes `/holocron:write`. Spawns the writer agent to produce manuscript prose, with project context loaded. argument-hint: "[chapter|scene|description]" --- Spawn the `writer` agent to produce manuscript prose for a chapter, scene, or freeform passage. This is the primary entry point for *generating* fiction — distinct from `/holocron:review` (feedback on existing prose) and `/holocron:edit` (line-level polish). ## Usage ``` /holocron:write 8 # Write chapter 8 /holocron:write next # Write the next chapter (per outline) /holocron:write continue # Continue the most recently modified chapter /holocron:write a scene where Kira finds the holocron # Freeform scene ``` ## How this dispatches 1. Resolve the scope: - Number → chapter file matching `chapters/0X-*.md` (create if missing). - `next` → consult `outline.md` and `progress.md`; identify the next undrafted chapter. - `continue` → most recently modified chapter under `chapters/`; resume from the last paragraph. - Freeform description → no chapter file; produce loose prose for the user to place. 2. Gather context the writer needs to stay coherent: - `architecture.md` (premise, theme, ending) — load if present. - `outline.md` (specifically the entry for this chapter) — load if present. - Character documents under `characters/` for any character in scope. - Era / world context: `world/era.md` and any relevant `world/factions/`, `world/locations/`, `world/lore-overlay/`. - Previous chapter's last 1-2 scenes — for voice continuity and to avoid repeating beats. - Tone guide: `craft/tone.md` if present. 3. Spawn the `writer` agent via the Task tool with `subagent_type: "holocron:writer"`. Pass the gathered context plus a clear directive (e.g., *"Draft chapter 8: Kira confronts Vrook in the Enclave archives. End on the apprentice's first lie."*). 4. The writer produces prose directly into the chapter file (it has Edit/Write tools). 5. After the writer returns, offer the user: *"Want to review what was written (`/holocron:review`), continue further, or make targeted revisions?"* ## Reference files the writer should consult The writer agent reads from `references/` for craft guidance. The most relevant for prose generation: - `references/prose-style.md` — sentence rhythm, POV integrity, voice - `references/dialogue.md` — dialogue craft - `references/scene-structure.md` — scene/sequel beats, MRUs - `references/craft-wisdom.md` — story craft principles - `references/star-wars-craft.md` — SW genre conventions, voice expectations - `references/old-republic-tone.md` — per-archetype voice, scene-mood calibration These are loaded by the writer as needed, not pre-loaded by this skill. ## When to use this vs. other commands - **`/holocron:write`** — *generate* new prose. Use for fresh chapters, fresh scenes, continuing a draft. - **`/holocron:review`** — feedback on prose already written. - **`/holocron:edit`** — line-level polish of a near-final chapter. - **`/holocron:critic <persona>`** — opinionated reader for a specific concern. - **`/holocron:plan`** / **`/holocron:outline`** — *before* writing, establish architecture and chapter beats. If the user asks to write but `architecture.md` or `outline.md` are missing, suggest running `/holocron:plan` and `/holocron:outline` first — writing without them tends to wander. ## Failure modes - **No project context.** If there's no `architecture.md`, no `outline.md`, no `chapters/` directory, the user is probably not inside a project. Ask them to run `/holocron:new` or `/holocron:go` first. - **Outline conflict.** If the user asks for chapter 8 but the outline ends at chapter 6, surface that and confirm before drafting beyond the outlined arc. - **Voice drift.** When continuing a draft, reread the last scene of the previous chapter before generating, so the writer matches the established register.
Versions
| Repository | Score | Licence |
|---|---|---|
| This page · petitchu/holocron | 100 | MIT |
| tw93/Waza | 100 | MIT |
| mimshins/ork | 100 | MIT |
| waynesutton/builder-skills | 100 | Apache-2.0 |
| iankiku/forwward-teams | 100 | MIT |
| nagisanzenin/idiolect | 100 | MIT |
| unclejobs-ai/second-claude-code | 96 | MIT |
| researai/deepscientist | 95 | Apache-2.0 |
| markusleben/ha-nova | 90 | MIT |
Database snapshot: 13.11.2026 · package version 933ca44bc3a4 (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 100story-draft
Use to draft a chapter or scene, take a turn, or act on "go" for a planned chapter. Follows drafting ownership and project voice; coaches when the writer drafts. Queues new facts for approval and supports bounded autopilot. - 100chapter-writing
This skill should be used when the user asks to "write a chapter", "next chapter", "chapter outline", "draft chapter", "continue the story", "write a scene", "outline a chapter", or wants to write prose for a story project. NOT for planning a scene's structure, subtext, or… - 100outline
This skill should be used when the user asks to "outline my book", "outline my novel", "break the story into chapters", "create a chapter breakdown", "outline book 2", "revise the outline", "I need a chapter list", or invokes `/holocron:outline`. Spawns the outliner agent to… - 100review
This skill should be used when the user asks to "review my chapter", "review chapter X", "review all chapters", "check this chapter for consistency issues", "this scene isn't working — help me fix it", "give me feedback on what I just wrote", "is chapter 8 ready to move on", or… - 100longform-fiction
Long-form fiction manuscript workflow that plans, drafts, or expands a novel, novella, or serial with a story bible, per-chapter contracts, parallel or sequential chapter workers, continuity checks, and word/character-count acceptance gates. Use when asked to write, draft,… - 100manuscript-reviser
Use when revising fiction prose that ALREADY EXISTS - a second/third-draft pass on a chapter or scene, a continuity or POV-consistency check, fixing a scene that drags, cutting dead weight, or tightening overwritten prose at the line level. Do NOT use to draft a brand-new scene…