orchestrator

Coordinate blog production by delegating tasks and managing Jira tickets across pipeline stages.

Updated May 6, 2026
One-click install
npx skills add https://github.com/Uniquecrete/ThinkFasterv1 --skill orchestrator-uniquecrete
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: orchestrator
Source: https://github.com/Uniquecrete/ThinkFasterv1/tree/main/Ops/AI-Blog-System/agents/orchestrator
Command: npx skills add https://github.com/Uniquecrete/ThinkFasterv1 --skill orchestrator-uniquecrete

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents delays and quality issues in an AI-powered blog production pipeline by coordinating research, content, distribution, and automation approvals with minimal owner intervention.

Core Features & Use Cases

  • Weekly pipeline planning & delegation: Runs a Monday sprint to create and assign Jira tickets across specialist agents in the correct dependency order (Research → Content → GEO → Social/Media/Marketing/Affiliate).
  • Operational health monitoring: Detects red flags like stalled agents, empty output directories, repeated errors, and prolonged Jira “In Progress” states, then retries with targeted fixes.
  • Controlled automation approvals: Reviews Developer Agent proposals and approves exactly 5 by transitioning Jira issues to the specified approval status, preserving quality and preventing over-automation.

Quick Start

Ask the AI to run the Orchestrator weekly planning sprint and produce the orchestration report while delegating Jira tickets to the Research, Content, GEO, Social, Media, Marketing, Affiliate, and Developer agents.

Frequently Asked Questions about orchestrator

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

FAQPage Schema
How do I coordinate an AI blog production pipeline across multiple specialist agents?

Coordinate an AI blog production pipeline by delegating tasks to specialist agents in dependency order, managing Jira tickets across stages, and applying operational health gates to detect stalled agents or repeated errors. This ensures minimal owner intervention while maintaining content quality.

How does workflow monitoring detect stalled agents or repeated errors in a content pipeline?

Workflow monitoring detects stalled agents by identifying empty output directories, repeated errors, and prolonged Jira In Progress states, then retries with targeted fixes before escalating to the owner for credential, revenue, brand-risk, or budget decisions.

What is the best way to automate Jira ticket creation for a weekly content sprint?

Automate Jira ticket creation for a weekly content sprint by running a Monday planning session that assigns tickets to Research, Content, GEO, Social, Media, Marketing, Affiliate, and Developer agents in the correct dependency order.

Can I limit automation approvals to prevent over-automation in my content pipeline?

Yes, you can limit automation approvals by reviewing Developer Agent proposals and approving exactly five by transitioning Jira issues to a specified approval status, preserving quality and preventing over-automation across the pipeline.

When should owner escalation happen during agent delegation?

Owner escalation should happen only for credential, revenue, brand-risk, or budget decisions during agent delegation. Routine pipeline health monitoring, retries, and Jira ticket transitions are handled automatically without owner intervention.