robertguss/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.
npx skills add https://github.com/robertguss/claude-code-toolkit --skill writing-orchestration
A complete orchestration system for complex writing workflows. This skill provides the strategic layer that coordinates agents, applies writing strategies, and ensures content quality.
This skill applies when:
Complex writing benefits from separation of concerns:
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
Before any content creation, apply this assessment:
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:
Question: "Do we know EXACTLY what message to convey?"
| Outcome | Action |
|---------|--------|
| ✓ Pass | Clear, specific communication goal |
| ✗ Fail | Need to interview for clarity |
Pass signals:
| Material | Message | Action |
|----------|---------|--------|
| ✓ | ✓ | Handoff to writer immediately |
| ✓ | ✗ | Interview for message clarity |
| ✗ | ✓ | Research/gather material |
| ✗ | ✗ | Interview for both |
These strategies apply to ALL content. Reference 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 |
Choose based on content type and goals. Reference situational-strategies.md for full list.
Before finalizing content, verify:
When creating new content:
When user provides feedback:
[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]
Only when:
/writing:planUses Orchestrator patterns:
/writing:draftUses Writer patterns:
/writing:reviewUses both:
/writing:compoundCaptures patterns that worked for future orchestration.
Take robertguss/writing-orchestration from the repository into ~/.claude/skills for personal
use, or into .claude/skills inside a project.
The agent identifies a skill by the name field in its header. Two skills with the
same name cannot sit side by side — one of them will be ignored.