Writing Staffing
Staff writer and outliner agents for fiction or long-form creative projects so drafts stay voice-consistent and beat-level structure exists before prose.
Overview
Writing-staffing is an agent skill most often used in Grow (also Build) that defines writer and outliner agent roles for creative prose pipelines.
Install
npx skills add https://github.com/haowjy/creative-writing-skills --skill writing-staffingWhat is this skill?
- writer agent: one writer per scene or chapter to preserve voice consistency across adjacent prose
- Two writer modes—autonomous draft/critique loops and interactive co-writing with the author
- outliner agent: arc, chapter, and beat structure plus mermaid diagrams for timelines and relationships
- Explicit handoff: outlines and scene beats feed the writer; drafts are not final until critique and revision
- Continuity anchors and character state files passed into each writing invocation
Adoption & trust: 1 installs on skills.sh; 241 GitHub stars; 2/3 security scanners passed (skills.sh audits); trending (+100% hot-view momentum).
What problem does it solve?
You are using one generic agent for story work and losing voice consistency, structure, and a clear draft-versus-final workflow.
Who is it for?
Authors and indie creators running multi-agent creative workflows with separate planning, drafting, and revision stages.
Skip if: Builders who only need a single marketing blurb or technical README without fiction-style arc and character continuity.
When should I use this skill?
Staffing creative writing agents when you need outlines before prose, scene-level drafting, or interactive co-writing with structured handoffs.
What do I get? / Deliverables
You staff outliner-then-writer agents with briefs, style files, and continuity inputs so structured outlines become critiqued drafts instead of one-shot chat prose.
- Scene or chapter drafts
- Arc and beat outlines with optional mermaid diagrams
- Structured inputs for critique-revision gates
Recommended Skills
Journey fit
Spans multiple journey phases - primary shelf plus alternate fits below.
Creative IP and serialized content compound in Grow when production pipelines—not one-off chats—ship chapters and arcs. Defines which builder agents produce outlines, scene drafts, and wiki artifacts, which is a content-production staffing pattern.
Where it fits
Map a three-act arc and chapter list before committing months of drafting effort.
Maintain wiki pages and continuity bibles alongside code for a narrative-driven game.
Run autonomous draft/critique loops to ship weekly serial chapters with one writer per installment.
Refresh character state files between arcs so returning readers see consistent motivation and facts.
How it compares
Use as a staffing playbook for specialized writing agents, not as a single prompt that both outlines and polishes in one pass.
Common Questions / FAQ
Who is writing-staffing for?
Solo creators and indie builders orchestrating fiction, serial content, or lore-heavy projects with multiple agent roles rather than one monolithic writer.
When should I use writing-staffing?
When starting a new arc and need chapter beats, before scene drafting, when visualizing timelines or relationships, or when co-writing interactively versus batch autonomous drafts.
Is writing-staffing safe to install?
It describes agent roles and file handoffs; review the Security Audits panel on this Prism page and treat generated drafts as private creative work until you publish.
SKILL.md
READMESKILL.md - Writing Staffing
# Builders Agents that produce written artifacts: prose, outlines, brainstorm reports, and wiki pages. ## writer Drafts prose from scene briefs and style files. One writer per scene or chapter: splitting the brief is better than parallelizing writers on the same content, because voice consistency degrades when multiple writers handle adjacent scenes independently. The writer's output is a draft, not final text. It goes through critique and revision before the orchestrator presents it. Pass the writer: - A scene brief or outline (what happens) - Relevant style files (how it should sound) - Continuity anchors (what came before) - Character state files for characters in the scene The writer operates in two modes: - **Autonomous**: receives a brief, produces a draft in the drafts directory. This is the mode used in draft/critique loops. - **Interactive**: back-and-forth with the author in conversation. Used when the author wants to co-write or iterate on specific passages. ## outliner Structures story at the arc, chapter, and beat level. Produces outlines and mermaid diagrams for arc structure, timeline visualization, and character relationship maps. Use the outliner when: - Starting a new arc and need to map the chapter structure - Breaking a chapter into scene beats before the writer drafts - Visualizing timeline or relationship complexity - The author has direction but needs it structured into a writable plan The outliner's output feeds the writer: a good outline is the single biggest input to draft quality. Skip outlining and the writer makes structural choices that the critic will flag and the revision will have to redo. The outliner does not brainstorm. For wide-open exploration and option generation before a direction is chosen, spawn the brainstormer instead. Outlining starts after the author has committed to a direction; brainstorming is how they get there. ## brainstormer Explores a question or angle in depth and produces a structured brainstorm report in the brainstorm directory. Tags speculative content with `<AI>`, preserves vagueness, presents options and tradeoffs rather than committing to a direction. Use the brainstormer when: - The author wants to explore ideas before choosing a direction - An orchestrator needs creative options from multiple angles (fan out brainstormers for diversity) - Testing "what if" scenarios before committing to structure - The question is open-ended and the answer shouldn't converge prematurely Brainstormer and outliner are complementary: brainstorm first to explore the space, then outline once a direction is chosen to lock it into structure the writer can build from. ## style-creator Creates style reference files from sample chapters, author requirements, or existing style files that need revision. Produces standalone style files: voice guides, scene technique guides, tonal register guides, and formatting conventions. Use the style-creator when: - The project needs voice files for a new POV character - Scene-type or tonal register guides don't exist yet and the writer needs them - Existing style files need updating because the voice has evolved over new chapters - The author has described a desired voice and wants it codified into a referenceable file The style-creator does not evaluate prose against styles. That's the critic with a voice focus: checking whether a draft maintains voice consistency, detecting drift, flagging register breaks. The style-creator's output is the reference material the critic's voice focus checks against. ## Wiki and Reference Pages For polished, reader-facing wiki pages, use the base @kb-writer. It writes to the author's wiki space with link discipline and citations back to chapters. For structural kb health (broken links, orphaned pages, relationship diagrams), use the base @kb-maintainer. # Character Simulation Character exploration through performance. The `character-sim` agent becomes a character for freeform conversation: the auth