writing-orchestration

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.

56 stars

Best use case

writing-orchestration is best used when you need a repeatable AI agent workflow instead of a one-off prompt.

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.

Teams using writing-orchestration should expect a more consistent output, faster repeated execution, less prompt rewriting.

When to use this skill

  • You want a reusable workflow that can be run more than once with consistent structure.

When not to use this skill

  • You only need a quick one-off answer and do not need a reusable workflow.
  • You cannot install or maintain the underlying files, dependencies, or repository context.

Installation

Claude Code / Cursor / Codex

$curl -o ~/.claude/skills/writing-orchestration/SKILL.md --create-dirs "https://raw.githubusercontent.com/robertguss/claude-code-toolkit/main/plugins/compound-writing/skills/writing-orchestration/SKILL.md"

Manual Installation

  1. Download SKILL.md from GitHub
  2. Place it in .claude/skills/writing-orchestration/SKILL.md inside your project
  3. Restart your AI agent — it will auto-discover the skill

How writing-orchestration Compares

Feature / Agentwriting-orchestrationStandard Approach
Platform SupportNot specifiedLimited / Varies
Context Awareness High Baseline
Installation ComplexityUnknownN/A

Frequently Asked Questions

What does this skill do?

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.

Where can I find the source code?

You can find the source code on GitHub using the link provided at the top of the page.

Related Guides

SKILL.md Source

# 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

Related Skills

writing-dna-discovery

56
from robertguss/claude-code-toolkit

Capture a writer's voice DNA through collaborative interview and sample analysis. Use when someone wants to document their writing voice for use with a ghost writer skill. Produces a Voice DNA Document with patterns, anti-patterns, and actionable guidance. Handles one register/mode per session, supports refinement over time.

pragmatic-writing

56
from robertguss/claude-code-toolkit

This skill should be used when writing technical content in the style of Hunt/Thomas (The Pragmatic Programmer) and Joel Spolsky (Joel on Software). It applies when creating technical essays, documentation, tutorials, or explanatory content that needs to be clear, engaging, and actionable.

dhh-writing

56
from robertguss/claude-code-toolkit

This skill should be used when writing in the distinctive style of David Heinemeier Hansson (DHH). It applies when creating blog posts, technical articles, business content, manifestos, or any prose requiring a clear, punchy, opinionated style.

ghost-writer

56
from robertguss/claude-code-toolkit

Produce first drafts that match a writer's authentic voice using their Voice DNA Document. Consumes DNA documents from writing-dna-discovery skill. Generates 2 meaningfully different drafts with headlines, confidence assessment, decision notes, and DNA refinement suggestions. Collaborative partner that evaluates, pushes back, and advocates for quality. Handles blog posts, essays, newsletters, and more.

chapter-architect

56
from robertguss/claude-code-toolkit

Plan and architect a single chapter at beat-level granularity. Use when you have a chapter from the Architecture Document and need to create a detailed outline before drafting. Produces a Chapter Outline Document for use by draft-coach or ghostwriter.

book-research-assistant

56
from robertguss/claude-code-toolkit

Plan, orchestrate, and validate deep research for nonfiction books. Use when an author has completed book architecture and needs to fill research gaps before outlining chapters. Triggers include requests to plan research, generate research prompts, validate research quality, or prepare for drafting. This skill does everything around deep research—planning, prompting, validating, synthesizing—but the actual research execution happens externally via Claude and Gemini deep research. Requires upstream documents from book-architect (Research Gaps Document, Master Architecture Document, Section Blueprints) and book-ideation (Book Concept Document).

book-market-research

56
from robertguss/claude-code-toolkit

Assess commercial viability of book concepts for Amazon KDP self-publishing. Use when the user has a Book Concept Document and wants to understand market demand, competition, pricing, and positioning before committing to write. Produces a Market Research Report with viability scorecard and Go/No-Go recommendation. Works standalone (commercial analysis only) or after idea-validator (integrated assessment). Nonfiction only.

book-ideation

56
from robertguss/claude-code-toolkit

Develop raw book ideas into structured nonfiction book concepts. Use when the user wants to develop a book idea, has brainstorm documents to refine into a book concept, wants to articulate a book's thesis/promise/reader/transformation, or needs to prepare a book concept for validation and market research. Nonfiction only. Produces a Book Concept Document with all elements needed for downstream skills (idea-validator, market-research, book-architect).

book-idea-validator

56
from robertguss/claude-code-toolkit

Stress-test book concepts against existing research before committing to architecture. Use when the user has a Book Concept Document ready for validation, wants to verify their thesis is defensible, needs to understand the competitive intellectual landscape, or wants honest assessment of their idea's strengths and weaknesses. Produces a Validation Report that informs the Go/No-Go decision. Nonfiction only.

book-architect

56
from robertguss/claude-code-toolkit

Design the structural and emotional architecture for nonfiction books. Use when an author has a validated book concept and needs to create the blueprint before drafting. Triggers include requests to structure a book, create a chapter outline, design a table of contents, map the reader's journey, or plan book organization. Requires upstream documents from book-ideation (Book Concept Document) and optionally from idea-validator (Validation Report) and market-research (Market Research Report).

paywall-pricing-optimizer

56
from robertguss/claude-code-toolkit

Design effective paywalls, structure subscription tiers, and optimize pricing for mobile apps. Covers monetization model selection, paywall screen design, pricing psychology, A/B testing strategy, and RevenueCat/StoreKit/Google Billing integration. Use when the user wants to monetize an app, design a paywall, choose between subscription vs one-time purchase, set pricing tiers, improve conversion rates, plan pricing experiments, or integrate in-app purchases. Triggers on "design my paywall", "how should I price my app", "subscription tiers", "monetization strategy", "paywall copy", "free trial length", "RevenueCat setup", "improve paywall conversion".

mobile-app-launch-checklist

56
from robertguss/claude-code-toolkit

Comprehensive step-by-step launch checklist for shipping mobile apps to the iOS App Store and Google Play Store. Covers pre-submission preparation, store asset creation, build and submission, launch day execution, and post-launch monitoring. Use when the user wants to launch a mobile app, prepare for App Store or Google Play submission, create a launch plan, review submission requirements, or ensure nothing is missed before releasing an app. Triggers on "launch checklist", "app submission", "prepare for launch", "app store submission", "google play submission", "ready to ship", "pre-launch review", "launch day plan".