Content Brief Batch Processor

Estimated time: 5-10 minutes per brief

This workflow runs deterministically over a directory of content briefs. It scans the briefs into a list, produces a full blog draft for each, humanizes the whole batch against the voice profile, and builds repurpose chains for email, LinkedIn, and X-thread. It is the bulk counterpart to the single-post publish flow.

Resolve the content corpus before running. In order: use any file or folder attached to the conversation (an exported brief bundle, CSV, or zip of markdown briefs) read from the workspace cwd; else read from a connected filesystem MCP server or a Google Sheets / Microsoft 365 export holding the brief list; else ask the user to attach the content briefs export. If no corpus resolves, stop and ask. Do not produce drafts from empty input.

Inputs: a briefs directory path (required) and an optional path to voice-notes.md (recommended).

When to Use

• User has a folder of content briefs to process at once
• User wants every brief turned into a humanized draft plus derivatives
• User wants a repeatable batch run, not an interactive single post

Workflow Steps

Step 1: Scan the Briefs (uses: content-audit)

Resolve and read the briefs directory, then list every brief found (markdown or JSON) into a structured brief list. If the corpus cannot be resolved, halt and ask the user to attach it. Do not continue on empty input.

• Input: briefs directory path
• Output: structured list of resolved briefs
• Key focus: a complete, validated brief list; halt on no input

Step 2: Produce Drafts (uses: content-blog)

For every brief in the list, produce a full blog draft, applying the voice profile if one was provided. Process the briefs as a batch and keep each draft mapped to its source brief. Halt on error rather than skipping silently.