delegation-check

Validates delegation prompts against agent role definitions for conflicts and missing contracts.

76|5|Updated Jul 7, 2026
One-click install
npx skills add https://github.com/catlog22/pi-maestro-flow --skill delegation-check-catlog22
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: delegation-check
Source: https://github.com/catlog22/pi-maestro-flow/tree/main/.pi/skills/delegation-check
Command: npx skills add https://github.com/catlog22/pi-maestro-flow --skill delegation-check-catlog22

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill checks whether workflow delegation prompts and agent role definitions are properly separated, helping prevent conflicts, duplication, and missing handoff contracts in multi-agent systems.

Core Features & Use Cases

  • Conflict Detection: Identifies role re-definition, domain expertise leakage, quality gate duplication, output format mismatches, process override, scope authority conflicts, and missing contracts.
  • Skill Quality Review: Reviews command-to-agent boundaries to keep prompts focused on objectives while preserving agent ownership of identity, process, and domain logic.
  • Use Case: Use this Skill when auditing a workflow skill or command file to ensure delegation prompts only specify the current task and the agent definition remains the single source of truth for behavior.

Quick Start

Ask for a delegation conflict check on the skill directory, command file, or agent pair you want reviewed.

Frequently Asked Questions about delegation-check

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

FAQPage Schema
How do I detect delegation prompt-role conflicts in a multi-agent workflow?

Delegation prompt-role conflicts are detected by validating delegation prompts against agent role definitions to find boundary violations and missing contracts. This requires a structured comparison of prompt objectives, agent responsibilities, output markers, and handoff completeness.

What delegation boundary violations should I check for when auditing multi-agent orchestration?

When auditing multi-agent orchestration, check for role re-definition, domain expertise leakage, quality gate duplication, output format mismatches, process override, scope authority conflicts, and missing contracts between the command prompt and the agent definition.

How do I review a workflow command file to ensure it only specifies the current task?

To review a command file, run a delegation conflict check to verify that delegation prompts only specify the current task. The agent definition must remain the single source of truth for identity, process, and domain logic.

When do I need a prompt design quality check for command-to-agent boundaries?

A prompt design quality check is needed when auditing a workflow skill or command file to ensure prompts are focused on objectives while preserving agent ownership of identity, process, and domain logic, preventing duplication and missing handoff contracts.

Can I use a delegation check on a specific agent pair in my workflow?

Yes, you can request a delegation conflict check on the specific skill directory, command file, or agent pair you want reviewed. The validation applies to command-to-agent workflow reviews and multi-agent orchestration audits.

Why does my multi-agent workflow have missing handoff contracts?

Missing handoff contracts occur when delegation prompts and agent role definitions are not properly separated. Validating prompt objectives, agent responsibilities, output markers, and handoff completeness identifies these gaps in multi-agent systems.