editorial-draft-review

To enqueue a markdown blog draft for editorial review, invoke the review command with your draft's slug. The system validates the site and slug, reads the markdown file, and creates an open DraftWorkflowItem to track the review iteration.

Submitting the same blog draft for editorial review twice is safe because the workflow creation is idempotent per site, slug, and content kind. It checks for disk-versus-version divergence and updates the existing open workflow item rather than creating duplicates.

A dev server is required to review an enqueued blog draft. After creating the DraftWorkflowItem, the skill exposes a dev review URL and provides clear guidance on server startup requirements so you can access the draft for annotation.

You can enqueue a placeholder markdown draft into the editorial review pipeline. The skill reads the draft markdown and handles placeholder bodies by providing actionable guidance within the status summary to help you complete the content.

The best way to track scattered blog drafts for annotation is to enqueue them into an editorial-review pipeline. This validates site slugs, reads markdown content, and creates tracked open workflow items, turning unmanaged drafts into structured review tasks.

Your editorial draft review workflow shows disk-versus-version divergence when the markdown file on disk has been modified differently from the tracked version. The skill detects this mismatch during idempotent workflow creation and alerts you to resolve the content discrepancy.