---
name: research-delivery-orchestrator
description: Use when the user wants an end-to-end research delivery workflow selected and coordinated from mixed inputs to final outputs such as intake, results brief, HTML delivery page, slides, expert review materials, or a final delivery bundle.
license: Proprietary - Medaibox Research Delivery Pack
---

# Research Delivery Orchestrator

## Overview

Use this skill as the routing layer for the Medaibox research delivery workflow.

This skill does not replace the specialized workflow skills. Instead, it inspects what already exists, identifies what is missing, and writes a clear execution route from current inputs to final delivery outputs.

## When to Use

Use this skill when:

- the user wants the whole delivery chain coordinated
- inputs are mixed and it is unclear which workflow step should start first
- some outputs already exist but the workflow is incomplete
- the user wants a plan to move from raw materials to final delivery bundle

## Expected Inputs

Typical inputs include:

- project directory
- `delivery_manifest.json`
- any existing workflow outputs such as intake, brief, HTML, slides, or review packet

## Expected Outputs

This skill should produce:

- `workflow_plan.md`
- `delivery_route.json`

## Workflow

1. Inspect the project directory and manifest.
2. Detect which workflow outputs already exist.
3. Decide the next required steps in the shortest valid order.
4. Write a markdown plan for human review.
5. Write a JSON route file for machine-readable orchestration.

## Reuse and Dependencies

This skill routes to:

- `research-results-intake`
- `results-summary-brief`
- `results-to-html-delivery`
- `results-to-slides`
- `expert-review-pack`
- `delivery-bundle-builder`

## Bundled Resources

Expected bundled resources:

- `scripts/route_delivery_workflow.py`
- `templates/workflow-plan.md`
- `references/workflow-routing-matrix.md`

## Quality Bar

Before finishing, confirm that:

- the plan matches the actual files currently present
- the next step list is actionable
- no completed stage is redundantly scheduled again without reason
- the JSON route is consistent with the markdown plan
