Skip to main content
skill CX Codex

editorial-workflow — Claude Code skill: what it does, how to install

editorial-workflow organizes newsroom production with story status taxonomies, assignment cards, deadline schedules, and edit handoff checklists.

MIT 252 installs ★ 458 updated 2026-10-24

Install into Claude Code · Skills CLI (Vercel) All methods and platforms ↓
npx skills add jamditis/claude-skills-journalism --skill editorial-workflow -a claude-code
Open on GitHub

What editorial-workflow does

The skill provides a structured framework for managing stories from pitch to publication. It defines explicit stages (Pitch, Assigned, Reporting, Draft, Edit, Revision, Copy, Final, Scheduled, and Published, alongside Hold and Kill options) and specifies whether the reporter, editor, or copy editor owns each step.

It embeds Markdown templates directly into the assistant's workflow. You get templates for story assignment cards, editorial planning meetings, publication calendars, and handoff notes between writers and editors. Because it relies purely on prompt guidance and Markdown structures, it requires no external database or API key.

What it helps with

  • track story progress across standardized editorial stages
  • generate assignment sheets with source and word count requirements
  • calculate reverse deadlines back from the target publication time
  • format structured edit notes and revision requests for reporters

Example prompts for the agent

  • Create an assignment record for an investigative piece on local transit funding due next Monday
  • Set up an editorial meeting lineup table for today's stories using editorial-workflow
  • Draft a missed deadline alert explaining a reporting blocker on the hospital feature

How to install editorial-workflow

1Skills CLI (Vercel)

npx skills add jamditis/claude-skills-journalism --skill editorial-workflow -a claude-code

2Manually: put the files in place

~/.claude/skills/editorial-workflow/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/editorial-workflow/

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

Questions about editorial-workflow

How to install editorial-workflow in Claude Code?

Run npx skills add jamditis/claude-skills-journalism --skill editorial-workflow -a claude-code in your terminal.

What is editorial-workflow used for?

It gives coding agents standard procedures and Markdown templates to manage newsroom assignments, calendars, and editor-reporter handoffs.

Does this skill require external software integrations?

No, it consists entirely of Markdown templates and workflow taxonomies stored in your local skill file.

Source text

SKILL.md · MIT
---
name: editorial-workflow
description: Manages newsroom editorial workflows. Use when tracking assignments, managing deadlines, or coordinating editorial calendars.
---

# 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-record info, etc.]

### Multimedia status
- Photos: [ready/pending/needed]
- Graphics: [ready/pending/needed]
```

### Editor → Reporter

When returning for revision:

```markdown
## Edit notes: [story title]

**Overall:** [brief assessment - on track, needs work, etc.]

### Structural changes needed
- [Major reorg, missing elements, etc.]

### Specific fixes
- Line [X]: [issue/change]
- Line [X]: [issue/change]

### Questions to resolve
- [Question requiring reporter input]

### Deadline for revisions
[date/time]

### Discussion needed?
[Yes - let's talk before you revise / No - changes are clear]
```

## Publication checklist

### Pre-publish checklist

```markdown
## Pre-publish: [story title]

### Content
- [ ] Headline is accurate and compelling
- [ ] Dek/subhead summarizes well
- [ ] Lede works
- [ ] All facts verified
- [ ] All sources attributed correctly
- [ ] Quotes are accurate
- [ ] Numbers double-checked

### Style
- [ ] AP Style applied
- [ ] Consistent voice throughout
- [ ] No typos or grammatical errors
- [ ] Appropriate length

### Legal/Ethics
- [ ] No defamation risk
- [ ] Sources of comment contacted
- [ ] Corrections from previous versions applied
- [ ] Embargoes respected

### Multimedia
- [ ] Photos have captions and credits
- [ ] Alt text added
- [ ] Video/audio plays correctly
- [ ] Graphics are accurate

### Metadata
- [ ] SEO headline filled
- [ ] Meta description written
- [ ] Tags/categories applied
- [ ] Author byline correct
- [ ] Publication date/time set

### Final sign-off
- [ ] Reporter reviewed final
- [ ] Editor approved
- [ ] Copy editor signed off
```

### Post-publish checklist

```markdown
## Post-publish: [story title]

### Immediate (within 1 hour)
- [ ] Story displays correctly
- [ ] Links work
- [ ] Images load
- [ ] No obvious errors
- [ ] Social posts scheduled/published

### Same day
- [ ] Monitor comments/feedback
- [ ] Watch for corrections needed
- [ ] Track initial metrics
- [ ] Respond to any issues

### Follow-up
- [ ] Note any updates needed
- [ ] Document corrections made
- [ ] Capture reader response
- [ ] Plan follow-up stories if warranted
```

## Workflow documentation

### Process documentation template

For documenting your newsroom's workflows:

```markdown
## Workflow: [Name of process]

### Purpose
[What this workflow accomplishes]

### When to use
[Triggers for this workflow]

### Roles involved
| Role | Responsibility |
|------|----------------|
| [Role] | [What they do] |

### Process steps

**Step 1: [Name]**
- Owner: [role]
- Action: [what happens]
- Output: [what's produced]
- Next: [what triggers next step]

**Step 2: [Name]**
[same format]

### Tools used
- [Tool]: [what it's used for]

### Templates/Forms
- [Link to templates]

### Exceptions
- [When normal process doesn't apply]
- [What to do instead]

### Escalation
- [When to escalate]
- [Who to contact]
```

### Onboarding new staff

```markdown
## Editorial workflow onboarding

### Day 1
- [ ] Access to CMS granted
- [ ] Added to editorial chat/channels
- [ ] Received style guide
- [ ] Introduced to direct editor

### Week 1
- [ ] Shadow experienced reporter
- [ ] Review workflow documentation
- [ ] Complete first assignment (low-stakes)
- [ ] Learn deadline expectations

### Month 1
- [ ] Independently handle standard assignments
- [ ] Know escalation paths
- [ ] Understand publication calendar
- [ ] Comfortable with all tools

### Key contacts
| Need | Contact |
|------|---------|
| Assignment questions | [name] |
| Technical issues | [name] |
| Editorial disputes | [name] |
| HR/Admin | [name] |
```

---

*Good workflows disappear. You only notice them when they break.*

© jamditis · MIT · jamditis/claude-skills-journalism

Similar skills

All skills for Writing and docs →

From the same set35

The whole set →
data-journalism Enforces data journalism standards to clean, verify, and document datasets with reproducible steps and an auditable public methodology. CX Codex +1 302installs newsletter-publishing newsletter-publishing guides newsletter setup, responsive HTML email formatting, and subscriber tracking workflows. CX Codex +1 292installs newsroom-style newsroom-style applies AP Style and newsroom standards when drafting news stories, editing press releases, or sharpening headlines. CX Codex +1 279installs document-design document-design builds print-ready HTML for PDF export with brand styling. Use it for reports, proposals, one-pagers, newsletters, slides, or flyers. CX Codex +1 255installs crisis-communications crisis-communications guides rapid fact-checking workflows and provides crisis communication templates under tight deadlines. CX Codex +1 232installs interview-prep interview-prep — a skill for journalists and researchers to prepare for interviews: research a source's background, design effective questions, and understand recording-consent laws across U.S. states. CX Codex +1 228installs foia-requests foia-requests is a Claude Code skill with references and templates for drafting U.S. federal and state public records requests under FOIA and state laws. CX Codex +1 228installs interview-transcription The interview-transcription skill turns interview recordings into timestamped transcripts and helps extract quotes. Use it when audio or video must be checked before publication. CX Codex +1 226installs

Project sponsors

Companies that keep this analytics open