orchestrate

Coordinates AI story execution through stages from TRIAGE to DELIVER.

1|Updated Mar 26, 2026

Search Tags:#workflow #design #pipeline #triage #escalation #orchestrate #story-map

Ready to run

npx skills add https://github.com/selcukyucel/north-starr-genai --skill orchestrate-selcukyucel

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: orchestrate
Source: https://github.com/selcukyucel/north-starr-genai/tree/main/skills/orchestrate
Command: npx skills add https://github.com/selcukyucel/north-starr-genai --skill orchestrate-selcukyucel

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Bridges the output of story decomposition to a functioning orchestration pipeline, routing stories through specialized agents, managing dependencies, detecting conflicts, and enabling human escalation when needed.

Core Features & Use Cases

End-to-end orchestration: routes stories through TRIAGE → DESIGN → PLAN → BUILD → HARDEN → DELIVER with stateful tracking.
Dependency and conflict management: detects blockers and coordinates parallel tasks while surfacing escalation points.
Logs and governance: maintains PIPELINE-STATUS.md, DECISIONS.md, and LEARNINGS.md for visibility and traceability.

Quick Start

Run /orchestrate after you have a story map from /decompose to start the live pipeline and begin processing stories.

Frequently Asked Questions about orchestrate

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

FAQPage Schema

How do I orchestrate AI story pipelines end-to-end with dependency tracking?▼

AI story pipelines are orchestrated end-to-end by routing decomposed stories through TRIAGE, DESIGN, PLAN, BUILD, HARDEN, and DELIVER gates. The pipeline manages dependencies, detects conflicts, and coordinates parallel tasks while maintaining state in PIPELINE-STATUS.md.

What's the best way to manage workflow escalation points in AI story pipelines?▼

Workflow escalation points in AI story pipelines are managed through human-in-the-loop gates within the orchestration pipeline. The system detects blockers and conflicts during task routing, surfacing them in DECISIONS.md logs for human intervention before proceeding.

How do I route decomposed stories through design and build agents?▼

Decomposed stories are routed through design and build agents using stepwise pipeline orchestration. Stories move sequentially from TRIAGE to DELIVER, with pipeline state tracked in .plans/PIPELINE-STATUS.md to coordinate agent handoffs and manage dependencies.

Can I run incremental pipeline processing for multiple stories with dependencies?▼

Incremental pipeline processing supports multiple stories with dependencies through the orchestration pipeline. It coordinates parallel tasks, manages budgets, and routes stories through TRIAGE, DESIGN, PLAN, BUILD, HARDEN, and DELIVER stages while tracking state across runs.

Do I need a story map from /decompose to start the orchestration pipeline?▼

A story map from /decompose is required to start the orchestration pipeline. The pipeline translates decomposed story maps into a live processing workflow, routing individual stories through specialized agents and gates with dependency and conflict management.

Why does pipeline state tracking matter for AI story orchestration?▼

Pipeline state tracking matters for AI story orchestration because it provides visibility and traceability across complex workflows. State is maintained in PIPELINE-STATUS.md, with decisions logged in DECISIONS.md and learnings captured in LEARNINGS.md for governance.