Skip to main content
ClaudeWave
Skill259 repo starsupdated 2d ago

editorial-workflow

The editorial-workflow skill provides templates and processes for newsrooms to track story assignments, manage deadlines, and coordinate between reporters and editors. It establishes a standardized story status taxonomy with twelve defined statuses, assignment record templates that document reporter, deadline, and story specifications, and handoff checklists to ensure clear communication when assigning stories. Use this skill when setting up story tracking systems, creating editorial calendars, establishing assignment protocols, managing multiple concurrent stories, or training new editors on newsroom operations.

Install in Claude Code
Copy
git clone --depth 1 https://github.com/jamditis/claude-skills-journalism /tmp/editorial-workflow && cp -r /tmp/editorial-workflow/journalism-core/skills/editorial-workflow ~/.claude/skills/editorial-workflow
Then start a new Claude Code session; the skill loads automatically.

SKILL.md

# Editorial workflow management

Newsrooms run on systems. This skill provides templates and processes for tracking stories, managing deadlines, and coordinating between reporters and editors.

## When to use

- Setting up story tracking systems
- Creating editorial calendars
- Establishing assignment and handoff protocols
- Managing multiple stories and deadlines
- Training new editors on workflow

## Story status taxonomy

### Standard statuses

| Status | Meaning | Owner |
|--------|---------|-------|
| **Pitch** | Idea submitted, awaiting approval | Reporter |
| **Assigned** | Approved, reporter working | Reporter |
| **Reporting** | Active reporting in progress | Reporter |
| **Draft** | First draft submitted | Editor |
| **Edit** | Editor making changes | Editor |
| **Revision** | Back with reporter for changes | Reporter |
| **Copy** | Copy editing stage | Copy editor |
| **Final** | Ready for publication | Editor |
| **Scheduled** | Queued for specific date | System |
| **Published** | Live | Complete |
| **Hold** | Paused, not abandoned | Editor |
| **Kill** | Story abandoned | Editor |

### Status flow

```
Pitch → Assigned → Reporting → Draft → Edit → Revision (loop) → Copy → Final → Scheduled → Published
                                         ↓
                                       Hold/Kill
```

## Story assignment tracking

### Assignment record template

```markdown
## Story: [Slug/working title]

### Assignment details
- **Reporter:** [name]
- **Assigning editor:** [name]
- **Date assigned:** [date]
- **Deadline:** [date/time]
- **Target publication:** [outlet/section]

### Story specs
- **Format:** [brief, feature, enterprise, etc.]
- **Word count:** [target]
- **Multimedia:** [photos, video, graphics needed]
- **Sources required:** [minimum sources]

### The assignment
[What the story is, angle, key elements to include]

### Key contacts
[Sources to interview, PR contacts, experts]

### Background/resources
[Links to previous coverage, documents, data]

### Budget line
[One sentence for editorial budget meetings]

### Status history
| Date | Status | Notes |
|------|--------|-------|
| [date] | Assigned | |
| [date] | [status] | [note] |
```

### Assignment handoff checklist

When assigning a story:

```markdown
## Assignment handoff

### From editor to reporter
- [ ] Story scope clearly defined
- [ ] Deadline confirmed
- [ ] Word count/format specified
- [ ] Key sources identified
- [ ] Background materials shared
- [ ] Multimedia needs discussed
- [ ] Questions answered

### Reporter confirms
- [ ] Deadline is realistic
- [ ] Have access to necessary sources
- [ ] Understand the angle
- [ ] Know who to ask for help
```

## Editorial calendar

### Calendar template

```markdown
## Editorial calendar: [Week/Month of Date]

### Monday [date]
| Time | Story | Reporter | Status | Notes |
|------|-------|----------|--------|-------|
| AM | [story] | [name] | [status] | |
| PM | [story] | [name] | [status] | |

### Tuesday [date]
[same format]

### Evergreen queue
| Story | Reporter | Ready date | Notes |
|-------|----------|------------|-------|
| [story] | [name] | [date] | [can run anytime after this] |

### Upcoming (next 2 weeks)
| Story | Reporter | Target date | Status |
|-------|----------|-------------|--------|
| [story] | [name] | [date] | [status] |
```

### Planning meeting template

For weekly/daily editorial meetings:

```markdown
## Editorial meeting: [date]

### Today's lineup
| Story | Reporter | Status | Publish time | Notes |
|-------|----------|--------|--------------|-------|
| [story] | [name] | [status] | [time] | |

### Tomorrow's lineup
[same format]

### In progress (due this week)
| Story | Reporter | Due | Status | Blockers |
|-------|----------|-----|--------|----------|
| [story] | [name] | [date] | [status] | [any issues] |

### Pipeline (next 2+ weeks)
| Story | Reporter | Target | Status |
|-------|----------|--------|--------|
| [story] | [name] | [date] | [status] |

### Discussion items
- [Topic 1]
- [Topic 2]

### Action items
- [ ] [Action] - [Owner] - [Deadline]
```

## Deadline management

### Deadline types

| Deadline | Purpose | Typical lead time |
|----------|---------|-------------------|
| **Reporting** | Complete interviews/research | 2-5 days before draft |
| **First draft** | Submit to editor | 24-48 hours before edit |
| **Final draft** | After revisions | 12-24 hours before copy |
| **Art/photos** | Visuals ready | Same as first draft |
| **Copy edit** | Language/style review | 4-8 hours before publish |
| **Publish** | Goes live | Set time |

### Deadline tracking template

```markdown
## Story: [title]
**Final publish deadline:** [date/time]

### Working backward
| Milestone | Deadline | Status |
|-----------|----------|--------|
| Reporting complete | [date] | ☐ |
| First draft due | [date] | ☐ |
| Art/photos due | [date] | ☐ |
| Edit complete | [date] | ☐ |
| Revisions due | [date] | ☐ |
| Copy edit complete | [date] | ☐ |
| Final review | [date] | ☐ |
| Schedule/publish | [date] | ☐ |
```

### Missed deadline protocol

When a deadline is at risk:

1. **Notify immediately** - Don't wait until the deadline passes
2. **Explain briefly** - What's blocking progress
3. **Propose new deadline** - Realistic estimate
4. **Offer alternatives** - Shorter version? Different angle?

```markdown
## Deadline alert

**Story:** [title]
**Original deadline:** [date/time]
**Issue:** [what's blocking]
**New proposed deadline:** [date/time]
**Impact:** [what this affects]
**Alternatives:** [options if any]
```

## Edit handoff protocols

### Reporter → Editor

When submitting draft:

```markdown
## Draft submission: [story title]

**Draft location:** [link/file]
**Word count:** [count]

### What's in the draft
- [Key points covered]

### What's still needed
- [ ] [Outstanding item]
- [ ] [Waiting for source callback]

### Questions for editor
- [Question about structure, angle, etc.]

### Source notes
[Any attribution issues, off-recor
accessibility-complianceSkill

Web accessibility patterns for news sites, journalism tools, and academic platforms. Use when building accessible interfaces, auditing existing sites for WCAG compliance, writing alt text for news images, creating accessible data visualizations, or ensuring content reaches all readers including those using assistive technologies. Essential for newsroom developers and anyone publishing web content.

electron-devSkill

Electron desktop application development with React, TypeScript, and Vite. Use when building desktop apps, implementing IPC communication, managing windows/tray, handling PTY terminals, integrating WebRTC/audio, or packaging with electron-builder. Covers patterns from AudioBash, Yap, and Pisscord projects.

mobile-debuggingSkill

Remote JavaScript console access and debugging on mobile devices. Use when debugging web pages on phones/tablets, accessing console errors without desktop DevTools, testing responsive designs on real devices, or diagnosing mobile-specific issues. Covers Eruda, vConsole, Chrome/Safari remote debugging, and cloud testing platforms.

one-way-doorSkill

Use this skill when creating new files that represent architectural decisions — data models, infrastructure configs, auth boundaries, API contracts, CI/CD pipelines, or event systems. Flags irreversible decisions and forces a discussion about trade-offs before committing.

python-pipelineSkill

Python data processing pipelines with modular architecture. Use when building content processing workflows, implementing dispatcher patterns, integrating Google Sheets/Drive APIs, or creating batch processing systems. Covers patterns from rosen-scraper, image-analyzer, and social-scraper projects.

test-first-bugsSkill

This skill should be used when the user reports a bug, describes unexpected behavior, says something is "broken", "not working", "failing", mentions an "error", "issue", or "problem" in code, or asks to "fix" something. Enforces test-driven bug fixing workflow.

vibe-codingSkill

Methodology for effective AI-assisted software development. Use when helping users build software with AI coding assistants, debugging AI-generated code, planning features for AI implementation, managing version control in AI workflows, or when users mention "vibe coding," Claude Code, Cursor, GitHub Copilot, Aider, Continue, Cline, Codex, Windsurf, or similar AI coding tools. Provides strategies for planning, testing, debugging, and iterating on code written with LLM assistance.

web-scrapingSkill

Web scraping with anti-bot bypass, content extraction, undocumented APIs and poison pill detection. Use when extracting content from websites, handling paywalls, implementing scraping cascades or processing social media. Covers requests, trafilatura, Playwright with stealth mode, yt-dlp and instaloader patterns.