/editorial-workflow
Manage editorial workflows for newsrooms and publications. Use when tracking story assignments, managing deadlines, coordinating editorial calendars, or establishing handoff protocols between reporters and editors. Includes templates for assignment tracking, editorial calendars,
$ npx -y skills add jamditis/claude-skills-journalism --skill editorial-workflow --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
- Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
- You can call itInvoke it directly when you want it.
- Slash command
/editorial-workflow
Context preview
The summary Claude sees to decide when to auto-load this skill.
Manage editorial workflows for newsrooms and publications. Use when tracking story assignments, managing deadlines, coordinating editorial calendars, or establishing handoff protocols between reporters and editors. Includes templates for assignment tracking, editorial calendars,
SKILL.md
editorial-workflow.SKILL.mdname: editorial-workflow
description: Manage editorial workflows for newsrooms and publications. Use when tracking story assignments, managing deadlines, coordinating editorial calendars, or establishing handoff protocols between reporters and editors. Includes templates for assignment tracking, editorial calendars, and workflow documentation.
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/KillStory assignment tracking
Assignment record template
## 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:
## 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
## 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:
## 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
## 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?
## 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:
Read more
name: editorial-workflow description: Manage editorial workflows for newsrooms and publications. Use when tracking story assignments, managing deadlines, coordinating editorial calendars, or establishing handoff protocols between reporters and editors. Includes templates for assignment tracking, editorial calendars, and workflow documentation.
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/KillStory assignment tracking
Assignment record template
## 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:
## 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
## 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:
## 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
## 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?
## 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:
A collection of Agent Skills for journalists, researchers, academics, media professionals, and communications practitioners. The same repository serves Claude Code and Codex while keeping Claude-only commands, agents, and hooks clearly labeled.
Repo: jamditis/claude-skills-journalism
Other skills on claude-skills-journalism.
- /accessibility-compliance
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
Open skill - /claude-md-updater
Use this skill when the user asks to update CLAUDE.md, save a lesson, or persist something from the current session: phrases like "update claude.md", "what should we remember", "save this lesson", or "add to context". Scans the conversation for hard-won lessons, new file paths,
Open skill - /electron-dev
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,
Open skill - /mobile-debugging
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 locally hosted Eruda and
Open skill - /one-way-door
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.
Open skill - /python-pipeline
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
Open skill

