omk-adaptorch-orchestration-review

Review DAG multi-agent orchestration designs for correctness, authority, and evidence-gating failures.

130|14|Updated Apr 30, 2026
One-click install
npx skills add https://github.com/dmae97/oh-my-kimi --skill omk-adaptorch-orchestration-review
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: omk-adaptorch-orchestration-review
Source: https://github.com/dmae97/oh-my-kimi/tree/main/templates/skills/agents/omk-adaptorch-orchestration-review
Command: npx skills add https://github.com/dmae97/oh-my-kimi --skill omk-adaptorch-orchestration-review

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps you review DAG-based multi-agent orchestration frameworks (like AdaptOrch and similar systems) to ensure correctness, bounded authority, and reproducible decision traces before you rely on them for coding workflows.

Core Features & Use Cases

  • DAG node contract verification: Check that each node has one responsibility, clear owner role, explicit inputs/outputs, and acceptance evidence.
  • Dependency edge correctness: Validate that edges represent real data or verification dependencies (not mere ordering) and that failed evidence blocks downstream work.
  • Worker authority and gate strength: Assess bounded write scope, merge boundaries, retry/timeout/fallback behavior, and evidence-gated repair paths.

Quick Start

Use it to generate a read-only verdict against a DAG orchestration design by reviewing node contracts, edges, authority boundaries, resilience gates, and decision trace replayability for a specific runtime.

Frequently Asked Questions about omk-adaptorch-orchestration-review

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

FAQPage Schema
How do I review DAG multi-agent orchestration designs for coding pipelines?

To review DAG multi-agent orchestration designs, validate node contracts for single responsibilities, verify dependency edges represent real data flows, and assess worker authority boundaries to produce a structured correctness verdict.

What is evidence-gated execution in multi-agent orchestration?

Evidence-gated execution in multi-agent orchestration blocks downstream work when required acceptance evidence is missing, ensuring failed nodes cannot trigger subsequent tasks without valid verification along the DAG dependency edges.

How do I assess worker authority risks in a DAG runtime scheduler?

Assess worker authority risks in a DAG runtime by checking bounded write scopes, validating merge boundaries, and reviewing fallback and retry timeout logic to ensure agents cannot exceed their designated permissions.

Why does my multi-agent orchestration lack reproducible decision traces?

Multi-agent orchestration lacks reproducible decision traces when DAG node contracts and coordinator boundaries omit replayable logs, preventing accurate reconstruction of the exact sequence of agent actions and evidence gates.

Can I use architecture review for retry timeout fallback logic in agent worktrees?

Yes, you can use architecture review to evaluate retry timeout fallback logic in agent worktrees by inspecting resilience gates, verifying evidence-gated repair paths, and ensuring bounded authority during recovery operations.

What are the limitations of reviewing DAG orchestration designs without explicit node contracts?

Reviewing DAG orchestration designs without explicit node contracts prevents accurate assessment of worker authority, dependency edge correctness, and decision trace replayability, leaving coding pipelines vulnerable to undetected merge boundary failures.