editorial-plan

Move editorial calendar entries from Ideas to Planned with site-specific framing.

Updated Jan 25, 2026
One-click install
npx skills add https://github.com/oletizi/audiocontrol.org --skill editorial-plan
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: editorial-plan
Source: https://github.com/oletizi/audiocontrol.org/tree/main/.claude/skills/editorial-plan
Command: npx skills add https://github.com/oletizi/audiocontrol.org --skill editorial-plan

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Move an editorial calendar entry from Ideas to Planned, applying site-specific framing to the title and dek while preparing keywords and topics for publication.

Core Features & Use Cases

  • Move entries between calendar stages (Ideas -> Planned) with updated framing.
  • Apply per-site voice guidelines to the title, dek, and description for consistent brand.
  • Read and write the per-site calendar file (docs/editorial-calendar-<site>.md) to persist changes.

Quick Start

Provide the article slug and optional --site, and let the skill move the entry to Planned with keyword/topic setup and voice-framing.

Frequently Asked Questions about editorial-plan

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I move an editorial calendar entry from Ideas to Planned with site-specific framing?

To move an editorial calendar entry to Planned, the skill reads the calendar, validates the target site, collects keywords and topics, and updates the file with new title, dek, and description framing.

How does site-aware voice framing work for editorial titles and descriptions?

Site-aware voice framing applies per-site guidelines to editorial titles and descriptions by consulting per-site topic hints from docs/editorial-channels-<site>.json and voice skill references before proposing the framing.

What do I need to set up before planning editorial topics for a specific site?

You need knowledge of the target site, access to per-site topic hints stored in docs/editorial-channels-<site>.json, and the per-site calendar file at docs/editorial-calendar-<site>.md to persist the updated entry.

Can I update keywords and topics when moving an editorial entry to Planned?

Yes, you can update keywords and topics when moving an entry to Planned. The process collects these elements during the transition and writes them into the per-site calendar file alongside the new framing.

What's the best way to automate editorial workflow transitions for multiple sites?

Automating editorial workflow transitions is handled by reading and writing the per-site calendar file, validating the target site, and applying site-specific framing to ensure brand consistency across different sites.

Why does my editorial calendar update require per-site topic hints?

Per-site topic hints are required because they provide the necessary site-specific context to accurately frame the title, dek, and description, ensuring the editorial entry matches the target site's voice and topics.