writing-staffing

Included with Lifetime

$97 forever

Team composition for writing workflows: which subagents to use, how many, what focus areas to assign, and how to scale effort. Use when composing critic panels, staffing draft/revise loops, or setting up brainstorm fan-outs.

Writing & Docs

What this skill does


# Writing Staffing

Compose the right team for each writing task. The goal is coverage across
perspectives: critics with different focus areas and brainstormers exploring
different angles. Avoid redundant passes from the same angle.

## General Principles

**Delegation keeps context clean.** Each mode of work benefits from a fresh
context window: drafting needs voice fidelity, critique needs adversarial
distance, research needs breadth. Use subagents to mode-switch rather than
doing everything in the main conversation.

**Review convergence.** Critic loops run until convergence (no new substantive
findings), not a fixed number of passes.

**Brainstorm diversity over brainstorm volume.** Three brainstormers exploring
different angles beats five exploring the same angle.

**Style creation and style evaluation are separate modes.** Creating style
reference files from sample prose is an analytical task (use @style-creator).
Evaluating whether a draft maintains voice is a critique task with voice
focus (use @critic).

## Effort Scaling

Effort scaling applies mainly to critics: the role that fans out within a
draft/revise cycle.

- Low-stakes drafts (brainstorm captures, wiki stubs): 1-2 critics
- Standard chapters: 3 critics with split focus areas
- Pivotal scenes (character deaths, reveals, arc climaxes): 4-5 critics

## Subagent Catalog

### Writers

- **@writer**: generative prose from briefs. One writer per scene/chapter.
  Use opus for voice fidelity.
- **@revision-writer**: surgical revision from critique findings. Preserves
  voice while fixing specific issues.
- **@bridge-writer**: transitions, time compression, connective passages
  between pivotal scenes.

### Critics and Reviewers

- **@critic**: adversarial prose critique. Fan out with different focus areas:
  voice, pacing, character, continuity. Sonnet default; use opus for
  final-pass on pivotal scenes.
- **@continuity-checker**: specialist: checks draft against canon files.
  Use when a scene references established facts.
- **@reader-sim**: experiential reading. Reports what it felt like to read
  the draft. Use for pivotal scenes or when something feels off but you can't
  name it. Opus for nuance.

### Exploration

- **@brainstormer**: wide-open idea exploration. Fan out for diversity.
- **@character-sim**: character voice performance. Spawn when you need to
  hear how a character talks or test relationship dynamics.
- **@outliner**: story structure at arc/chapter/beat levels.
- **@style-creator**: analyzes prose and produces style reference files.

### Knowledge

- **@chronicler**: extracts facts from chapters into the kb. Cheap (haiku)
  and focused.

## Parallelism

Think about what depends on what:

- Critics need a finished draft: they wait for the writer
- Critics examine different dimensions: fan them all out simultaneously
- Brainstormers are independent: fan them out
- Character simulations in a multi-character scene are independent: fan out
- Chronicler runs after a chapter is finalized, not during drafting

Files: 1

Size: 3.2 KB

Complexity: 7/100

Category: Writing & Docs

Source: https://github.com/haowjy/creative-writing-skills/tree/main/cw/skills/writing-staffing

Related in Writing & Docs

jax-development

Included

Use this skill when the user is writing, debugging, profiling, refactoring, reviewing, benchmarking, parallelising, exporting, or explaining JAX code, or when they mention JAX, jax.numpy, jit, grad, value_and_grad, vmap, scan, lax, random keys, pytrees, jax.Array, sharding, Mesh, PartitionSpec, NamedSharding, pmap, shard_map, Pallas, XLA, StableHLO, checkify, profiler, or the JAX repo. It helps turn NumPy or PyTorch-style code into pure functional JAX, fix tracer/control-flow/shape/PRNG bugs, remove recompiles and host-device syncs, choose transforms and sharding strategies, inspect jaxpr/lowering/IR, and benchmark compiled code correctly.

Writing & Docsscripts

nature-article-writer

Included

Drafts, rewrites, diagnostically critiques, and style-calibrates primary research manuscripts for Nature and Nature Portfolio journals. Use when the user wants a Nature-style title, summary paragraph or abstract, introduction, results, discussion, methods, figure legends, presubmission enquiry, cover letter, reviewer response, or when a scientific draft sounds generic, jargon-heavy, structurally weak, or AI-ish and needs precise, broad-reader-friendly prose without inventing data, analyses, or references. Best for primary research articles and letters rather than reviews or press releases unless explicitly adapting one.

Writing & Docsscripts

deckrd

Included

Document-driven framework that derives requirements, specifications, implementation plans, and executable tasks from goals through structured AI dialogue. Use when user says "write requirements", "create spec", "plan implementation", "derive tasks", "structure this feature", "break down into tasks", or "document this module". Also use for reverse engineering existing code into docs (/deckrd rev). Do NOT use for direct code writing — use /deckrd-coder after tasks are generated. Do NOT use when the user only wants to run or fix existing code without planning.

Writing & Docsscripts

clinical-decision-support

Included

Generate professional clinical decision support (CDS) documents for pharmaceutical and clinical research settings, including patient cohort analyses (biomarker-stratified with outcomes) and treatment recommendation reports (evidence-based guidelines with decision algorithms). Supports GRADE evidence grading, statistical analysis (hazard ratios, survival curves, waterfall plots), biomarker integration, and regulatory compliance. Outputs publication-ready LaTeX/PDF format optimized for drug development, clinical research, and evidence synthesis.

Writing & Docsscripts

handling-sf-data

Included

Salesforce data operations with 130-point scoring. Use this skill to create, update, delete, bulk import/export, generate test data, and clean up org records using sf CLI and anonymous Apex. TRIGGER when: user creates test data, performs bulk import/export, uses sf data CLI commands, needs data factory patterns for Apex tests, or needs to seed/clean records in a Salesforce org. DO NOT TRIGGER when: SOQL query writing only (use querying-soql), Apex test execution (use running-apex-tests), or metadata deployment (use deploying-metadata).

Writing & Docsscripts

accelint-ac-to-playwright

Included

Convert and validate acceptance criteria for Playwright test automation. Use when user asks to (1) review/evaluate/check if AC are ready for automation, (2) assess if AC can be converted as-is, (3) validate AC quality for Playwright, (4) turn AC into tests, (5) generate tests from acceptance criteria, (6) convert .md bullets or .feature Gherkin files to Playwright specs, (7) create test automation from requirements. Handles both bullet-style markdown and Gherkin syntax with JSON test plan generation and validation.

Writing & Docsscripts