skills.rest
ylxmf2005
ylxmf2005COMMUNITY
Explore all skills by this author →
GitHub

delivery-orchestrator

Enforce gate-based evidence and accountability across AgentCorp delivery pipelines.

11|1|Updated Mar 3, 2026
Search Tags:#workflow#orchestration#artifacts#evidence#gates#delivery#sponsor
One-click install
npx skills add https://github.com/ylxmf2005/AgentCorp --skill delivery-orchestrator
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: delivery-orchestrator
Source: https://github.com/ylxmf2005/AgentCorp/tree/main/agentcorp/delivery-orchestrator
Command: npx skills add https://github.com/ylxmf2005/AgentCorp --skill delivery-orchestrator

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

Gate-driven orchestration for complex delivery pipelines, ensuring every progress step is backed by inspectable evidence rather than claims.

Core Features & Use Cases

  • Gate-based routing: classify work, assign phases to the correct AgentCorp role, and enforce evidence at every handoff.
  • Evidence-centric progress: progress only when artifacts, links, or excerpts are attached and reviewable by sponsors.
  • Host-agnostic orchestration: coordinates Claude Code and Codex runtimes, lands decisions, and tracks ownership via manifests.

Quick Start

Provide the initial task context and your desired mode, pace, and language to begin orchestrating the delivery through the gate-driven pipeline.

Frequently Asked Questions about delivery-orchestrator

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

FAQPage Schema
How do I enforce evidence and accountability at every stage of a delivery pipeline?▼

Gate-based orchestration enforces evidence and accountability in a delivery pipeline by requiring artifacts, links, or excerpts to be attached and reviewable before any progress step is approved. This ensures every handoff is backed by inspectable evidence rather than claims.

What is gate-based routing in delivery management?▼

Gate-based routing classifies work, assigns phases to the correct role, and enforces evidence at every handoff. It ensures sponsors can review artifacts and blockers are resolved before progress continues.

How do I orchestrate delivery tasks across different runtime environments?▼

Host-agnostic orchestration coordinates Claude Code and Codex runtimes, lands decisions, and tracks ownership via manifests to ensure consistent gate-based lifecycle management across platforms.

Can I customize the pace and effort level of a workflow orchestration pipeline?▼

You can customize workflow orchestration pace and effort by specifying mode, pace, and language constraints through frontmatter, allowing continuous or guided pace and low to max effort while preserving strict gate-based lifecycle rules.

When do I need a manifest for delivery pipeline tasks?▼

A manifest is needed for delivery pipeline tasks when tracking ownership and routing responsibilities across different roles, ensuring artifacts and blockers are resolved and providing an audit trail for sponsors before progress is permitted.

Related Skills

Explore More Product & Management Skills→
pandazkipandazki
154

pneuma-preferences

Maintain persistent user preferences across sessions to guide design decisions.

Community
Advanced
Atrium-HermesAtrium-Hermes

Janitor

Delete stale .notify-*, .pending-notify-temp, and .outputs artifacts by TTL.

Community
Intermediate
furedeafuredea
1

skill-auditor

Audit Claude Code or Codex skill portfolios for routing errors and coverage gaps.

Community
Advanced
LoxtepIncLoxtepInc
1

governance-policies

Author and manage deploy-time governance policies via the REST API.

Official
Advanced