blog-orchestrator

Orchestrates a multi-agent workflow to develop, publish, and maintain a technical blog.

Updated Apr 9, 2026
One-click install
npx skills add https://github.com/jjc4480/my-blog --skill blog-orchestrator
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: blog-orchestrator
Source: https://github.com/jjc4480/my-blog/tree/main/.claude/skills/blog-orchestrator
Command: npx skills add https://github.com/jjc4480/my-blog --skill blog-orchestrator

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

기술블로그 에이전트를 조율하여 개발/운영 작업을 자동화하고, 여러 하위 에이전트 간의 협업을 관리합니다. 이 스킬은 블로그 기능 구현, 페이지 추가, 컴포넌트 개발, 콘텐츠 파이프라인 구성, 배포 작업을 포함한 전체 워크플로를 하나의 조정 엔진으로 처리합니다.

Core Features & Use Cases

  • 독립적인 하위 에이전트 세트(frontend-dev, content-engine, infra-deploy, qa-verifier)를 동시 실행하고 출력 경로를 관리합니다.
  • Phase 1~4의 워크플로우를 정의하고, Phase 2의 팬아웃 실행과 Phase 3의 QA 검증 루프를 지원합니다.
  • 작업 디렉토리 관리(_workspace/) 생성, 변경 파일 목록 보고, 재실행 루프를 통한 수정 피드백을 제공합니다.

Quick Start

블로그 초기 셋업 요청에 대해 4개 에이전트를 병렬로 조정하고 QA를 거쳐 최종 보고를 완료하라.

Frequently Asked Questions about blog-orchestrator

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

FAQPage Schema
How do I automate blog development and deployment using multiple agents?

Multi-agent blog automation orchestrates four subagents—frontend-dev, content-engine, infra-deploy, and qa-verifier—to coordinate blog feature implementation, content pipelines, and deployment across defined workflow phases.

What is the best way to manage parallel execution of blog content pipelines and frontend components?

Parallel blog content pipeline execution fans out tasks in Phase 2, allowing independent subagents for frontend development and content generation to run simultaneously while managing output paths within a dedicated workspace directory.

How does QA verification work in an automated blog deployment workflow?

QA verification in a blog deployment workflow runs a qa-verifier subagent during Phase 3, checking changed files and entering a retry loop that provides modification feedback until all quality checks pass before final reporting.

Can I use workflow orchestration to maintain a technical blog without manual intervention?

Workflow orchestration automates technical blog maintenance by coordinating subagents across four phases, handling everything from feature implementation and page additions to content pipeline configuration and deployment with automated reporting.

What limitations exist when coordinating multiple agents for blog infrastructure deployment?

Multi-agent blog orchestration requires managing workspace directories and tracking changed file lists, with limitations around retry loop feedback handling and ensuring subagent outputs remain isolated during parallel execution phases.

Do I need predefined prompts to set up a multi-agent blog content pipeline?

Multi-agent blog content pipelines rely on defined prompts for each subagent—frontend-dev, content-engine, infra-deploy, and qa-verifier—to ensure coordinated execution, proper workspace management, and structured QA reporting.