blog-post

To write SEO-optimized blog posts with generated cover images, delegate research to a subagent, save findings to a research file, write the structured post to a specific slug directory, and use a generate_cover tool for the hero image asset.

The required file structure for publishing generated blog content organizes outputs under a specific slug directory. Your markdown post must be saved as post.md and the matching generated cover image must be saved as hero.png inside that blog folder.

Yes, you need a researcher subagent to generate long-form articles. The workflow mandates delegating research tasks to a subagent that saves findings to a research file, which must be read before composing the final SEO-optimized blog post.

Yes, you can use this workflow to create technical tutorials and product guides. It is designed for content teams and solo writers producing research-backed content, applying an enforced output structure and SEO checklist to validate completeness for publishing workflows.

The best way to ensure keyword placement in generated blog posts is using the built-in SEO and quality checklist. This process validates concise titles, meta descriptions, sectioned content, and proper keyword placement before the article is considered complete.

Your blog generation workflow requires a matching cover image to remove manual coordination between research, writing, and asset creation. A post is only considered complete when a generated hero.png asset is saved inside the blog folder.