blog-post-author

To draft a publish-ready blog post from a brief, you need a workflow that converts the filled brief into a complete draft while generating a dispatchable set of per-asset tasks for subagents. This ensures the post stays within the brief's scope.

An asset-task bundle for blog content creation is a cohesive set of dispatch-ready files generated for each declared output, such as hero images, OG cards, social posts, embedded diagrams, code samples, internal-link maps, and newsletter excerpts.

Yes, you can generate social posts and OG cards from a single blog brief by creating an asset-task bundle. The workflow emits one dispatch-ready task file per declared asset, serializing them for subagents to execute independently.

To validate blog post consistency against the original brief, the content creation workflow runs a final quality gate report after all asset tasks complete, ensuring the post preserves the original scoped boundaries and voice.

The best way to coordinate subagent tasks for blog asset generation is to serialize tasks as separate files within a cohesive bundle, coordinating task sequencing to ensure proper mutations like internal-link maps and pull quotes before a final quality gate.

A brief-to-post workflow handles internal-link maps and pull quotes by coordinating task sequencing during asset generation. This ensures proper mutations are applied to the post draft before producing the final quality gate report.