Skip to main content
skill CX Codex

writing-orchestration — Claude Code skill: setup and workflow

Coordinates multi-stage content creation between two agents, checks research completeness before drafting, and enforces 10 baseline style rules.

Install into Claude Code · Skills CLI (Vercel) All methods and platforms ↓
npx skills add robertguss/claude-code-toolkit --skill writing-orchestration -a claude-code
Open on GitHub

What writing-orchestration does

This skill implements a phased drafting pipeline inspired by the Spiral Writing System. It separates work between an Orchestrator and a Writer. The Orchestrator classifies incoming requests, gathers sources, and confirms readiness. Crucially, the Orchestrator never writes text directly, which keeps factual synthesis separate from drafting.

Before any copy gets generated, the pipeline executes a two-gate readiness check. Gate 1 confirms material sufficiency by checking for concrete examples, quotes, and data points so the model does not invent claims. Gate 2 verifies message clarity through a single-sentence thesis and a defined target audience. If either gate fails, the agent pauses drafting to gather more background or interview the user.

The Writer produces content using 10 non-negotiable baseline writing rules, such as active present verbs and one idea per sentence. For new articles in EXPLORATION mode, it returns 3 distinct drafts with differing angles rather than minor wording tweaks.

What it helps with

  • Split research gathering and draft creation between distinct agents
  • Stop drafts from hallucinating missing facts via readiness gates
  • Generate three distinct angles for new topic drafts
  • Apply ten baseline writing rules to strip weak adverbs and passive voice

Example prompts for the agent

  • Run /writing:plan for an engineering blog post about database migration
  • Evaluate material readiness and draft three exploratory intros for our release notes
  • Revise this technical brief in REFINEMENT mode according to team feedback

How to install writing-orchestration

1Skills CLI (Vercel)

npx skills add robertguss/claude-code-toolkit --skill writing-orchestration -a claude-code

2Manually: put the files in place

~/.claude/skills/writing-orchestration/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/writing-orchestration/

Step by step, with commands for each platform: How to install skills in Claude Code: five ways

Questions about writing-orchestration

How to install writing-orchestration in Claude Code?

Run npx skills add robertguss/claude-code-toolkit --skill writing-orchestration -a claude-code in your project terminal.

What does the writing-orchestration skill do?

It establishes an orchestration architecture where an Orchestrator agent assesses fact readiness before a Writer agent drafts content using 10 baseline stylistic strategies.

How does the two-gate assessment work?

Gate 1 verifies that enough concrete data and examples exist to prevent fabrication. Gate 2 confirms the thesis and target audience are clearly defined before the writer receives the task.

Source text

SKILL.md · MIT
---
name: writing-orchestration
description: This skill should be used when orchestrating complex writing workflows with multiple phases. It provides two-agent orchestration patterns, the two-gate content readiness assessment, 10 baseline writing strategies, 20+ situational strategies, and quality checkpoints. Inspired by the Spiral Writing System.
---

# Writing Orchestration Skill

A complete orchestration system for complex writing workflows. This skill provides the strategic layer that coordinates agents, applies writing strategies, and ensures content quality.

## When to Use This Skill

This skill applies when:
- Coordinating multiple writing agents
- Applying strategic writing decisions
- Assessing content readiness before drafting
- Selecting and applying writing strategies
- Running quality checkpoints on drafts

## Two-Agent Architecture

Complex writing benefits from separation of concerns:

### Orchestrator Role
- Classifies requests (information vs. content)
- Applies two-gate assessment
- Gathers research and context
- Hands off to writer when ready
- Never creates content directly

### Writer Role
- Creates drafts using strategies
- Applies style guides
- Produces variations (EXPLORATION mode)
- Refines based on feedback (REFINEMENT mode)
- Uses tools for all content (never in chat)

```
User Request
    ↓
[Orchestrator] → Classify → Research → Two-Gate Assessment
    ↓
    ├── Not Ready → Gather more material/clarity
    ↓
    └── Ready → Handoff to Writer
                    ↓
              [Writer] → Apply Strategies → Create Drafts
                    ↓
              Quality Checkpoints → Output
```

## Two-Gate Content Readiness Assessment

Before any content creation, apply this assessment:

### Gate 1: Material Sufficiency

**Question**: "Could the writer create this without inventing facts?"

| Outcome | Action |
|---------|--------|
| ✓ Pass | Have concrete examples, data, quotes available |
| ✗ Fail | Need to research/gather material first |

**Pass signals**:
- Specific examples available
- Data points confirmed
- Expert quotes accessible
- No major claims need fabrication

### Gate 2: Message Clarity

**Question**: "Do we know EXACTLY what message to convey?"

| Outcome | Action |
|---------|--------|
| ✓ Pass | Clear, specific communication goal |
| ✗ Fail | Need to interview for clarity |

**Pass signals**:
- Can state thesis in one sentence
- Know the audience specifically
- Know the desired action
- Angle is differentiated

### Decision Matrix

| Material | Message | Action |
|----------|---------|--------|
| ✓ | ✓ | Handoff to writer immediately |
| ✓ | ✗ | Interview for message clarity |
| ✗ | ✓ | Research/gather material |
| ✗ | ✗ | Interview for both |

## 10 Baseline Strategies (ALWAYS Apply)

These strategies apply to ALL content. Reference [baseline-strategies.md](./references/baseline-strategies.md) for full details.

| Strategy | Rule | Transform |
|----------|------|-----------|
| **reader-zero-context** | Add 3-6 word orienting phrases | "Stripe handles billing" → "Stripe, the payments platform, handles billing" |
| **subject-verb** | Subject + verb in first 5 words | "There were students who..." → "Students completed..." |
| **activate-verbs** | Precise verbs over is/was | "Markets were down" → "Markets plunged" |
| **watch-adverbs** | Let strong verbs carry load | "whispered quietly" → "whispered" |
| **limit-ings** | Simple tense over continuous | "are running tests" → "run tests" |
| **prefer-simple** | Everyday language unless technical | "utilizes stochastic gradient" → "learns by trial and error" |
| **cut-big-small** | Edit hierarchically | Paragraphs → Sentences → Words |
| **ban-empty-hypophora** | No self-answered questions | "The payoff? Our app..." → "Our app..." |
| **present-active-tense** | Direct, immediate language | "debuts today" → "is out now" |
| **one-idea-per-sentence** | Single clear point | Split compound thoughts |

## 20+ Situational Strategies (Select 3-4)

Choose based on content type and goals. Reference [situational-strategies.md](./references/situational-strategies.md) for full list.

### Hook & Opening
- **hook-effectiveness** - Counterintuitive or surprising openings
- **tension-builder** - Create and resolve tension
- **pattern-twist** - Set expectations, then break them

### Structure & Flow
- **order-words-emphasis** - Important words at sentence ends
- **sentence-length** - Vary for rhythm (short for impact, long for flow)
- **paragraph-length** - Mix for visual rhythm
- **ladder-abstraction** - Alternate concrete ↔ abstract

### Style & Voice
- **elegant-variation** - Avoid word repetition
- **passive-aggressive** - Strategic passive for emphasis
- **punctuation-pace** - Use punctuation for rhythm
- **key-words-space** - Give important terms breathing room

### Persuasion & Engagement
- **essential-name-filter** - Only names that add value
- **name-of-dog** - Specific details for authenticity
- **original-images** - Fresh metaphors, avoid clichés
- **show-and-tell** - Balance showing with telling

### Narrative & Story
- **narrate-scenes** - Immersive scene-setting
- **cinematic-angles** - Camera-like perspective shifts
- **dialogue-compression** - Tight, purposeful dialogue
- **reveal-traits** - Character through action

## Quality Checkpoints

Before finalizing content, verify:

### Opening Quality
- [ ] Opening is counterintuitive or surprising
- [ ] Leads with most compelling insight/moment/problem
- [ ] No chronology/setup/version numbers in opening
- [ ] Hook earns the next sentence

### Body Quality
- [ ] Body delivers on opening's promise
- [ ] Concrete sensory details present
- [ ] Each paragraph has clear purpose
- [ ] Transitions are smooth

### Strategy Compliance
- [ ] All 10 baseline strategies applied
- [ ] 3-4 situational strategies visible
- [ ] Each sentence expresses one clear idea
- [ ] Technical terminology oriented with context

### Style Guide Compliance
- [ ] Voice matches profile/guide
- [ ] No prohibited words/patterns
- [ ] Formatting rules followed

## Content Modes

### EXPLORATION Mode (New Content)

When creating new content:
1. Generate 3 different drafts
2. Vary angle, not just words
3. Apply all strategies to each
4. Let user choose direction

### REFINEMENT Mode (Editing)

When user provides feedback:
1. Work with existing draft
2. Preserve voice and structure
3. Apply specific changes requested
4. Keep what works

## Handoff Protocol

### Orchestrator → Writer

```
[Research summary if applicable - 2-3 sentences]
[Material gathered: list key assets]
[Message clarity: thesis statement]
[Style guide: name if applicable]
[Mode: EXPLORATION or REFINEMENT]
```

### Writer → Orchestrator (Rare)

Only when:
- User explicitly requests brainstorming
- New research topic needed
- Web search required
- Significant scope change

## Integration with Commands

### `/writing:plan`
Uses Orchestrator patterns:
- Request classification
- Research phase
- Two-gate assessment
- Material gathering

### `/writing:draft`
Uses Writer patterns:
- Strategy application
- Mode selection
- Draft creation
- Quality checkpoints

### `/writing:review`
Uses both:
- Orchestrator: coordinate review agents
- Writer: apply fixes

### `/writing:compound`
Captures patterns that worked for future orchestration.

## References

- [baseline-strategies.md](./references/baseline-strategies.md) - Full 10 baseline strategies with examples
- [situational-strategies.md](./references/situational-strategies.md) - 20+ situational strategies
- [quality-checkpoints.md](./references/quality-checkpoints.md) - Detailed checkpoint criteria

© robertguss · MIT · robertguss/claude-code-toolkit

Similar skills

All skills for Writing and docs →

From the same set20

voice-capture Analyze writing samples and turn their style into a reusable voice profile. Use it to document a brand voice or guide new writing toward a specific author’s style. CX Codex +1 ★ 132repo stars pragmatic-writing A skill that pushes the agent toward the prose style of The Pragmatic Programmer and Joel on Software. Useful for essays, docs and tutorials. CX Codex +1 ★ 132repo stars every-style-editor This skill audits articles, newsletters, and blog posts against Every's writing standards. It reviews copy line by line to catch grammar issues and formatting slips. CX Codex +1 ★ 132repo stars dhh-writing This skill guides an agent toward bold, direct prose for articles, business writing, and manifestos. Use it when a draft needs a clear stance and concrete arguments. CX Codex +1 ★ 132repo stars writing-dna-discovery A skill that interviews you and reads your samples to build a voice document a ghost writer skill can follow. CX Codex +1 ★ 132repo stars ghost-writer Creates two distinct first drafts matching personal writing style from a Voice DNA Document. Useful for crafting articles and newsletters. CX Codex +1 ★ 132repo stars chapter-architect This skill turns a high-level chapter brief into a beat-level outline. It helps shape the reader’s journey before drafting while leaving room for author decisions. CX Codex +1 ★ 132repo stars book-research-assistant A skill that plans and vets research for a nonfiction book: turns fact gaps into questions, writes the prompts, and rules on each source. CX Codex +1 ★ 132repo stars

Project sponsors

Companies that keep this analytics open
Gold sponsor

Impressions, clicks and code copies — open statistics. We keep the numbers public for the same reason NeBlask itself is public. Become a sponsor