One-click install
npx skills add https://github.com/tcytan/tecton --skill delegation-check
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: delegation-check
Source: https://github.com/tcytan/tecton/tree/main/.claude/skills/delegation-check
Command: npx skills add https://github.com/tcytan/tecton --skill delegation-check

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps you detect when command delegation prompts (Agent() calls) accidentally redefine an agent’s identity, leak domain expertise, duplicate quality gates, conflict on output/return contracts, or override an agent’s process—causing inconsistent behavior and brittle workflows.

Core Features & Use Cases

  • Delegation boundary validation: Ensures commands own WHAT/WHERE while agents own WHO/HOW, matching the intended separation of concerns.
  • 7-dimension conflict detection: Flags role re-definition, domain expertise leaks, quality gate duplication, output format/marker conflicts, process override, scope authority conflicts, and missing contracts.
  • Actionable repair guidance: Produces per command↔agent findings plus fix recommendations and an overall verdict (CLEAN/REVIEW/CONFLICT).
  • Use cases: Workflow maintenance and review when adding/modifying skills, commands, or agents; regression checks before releasing orchestration changes.

Quick Start

Ask the AI to run a delegation conflict scan for the entire skills and commands scope.

Frequently Asked Questions about delegation-check

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

FAQPage Schema
How do I prevent prompt delegation from overriding agent role definitions?

To prevent prompt delegation from overriding agent role definitions, you can run a static analysis scan that validates command and agent pairs against content separation boundaries, producing a per-pair verdict and fix recommendations for any boundary violations found.

What is a delegation boundary leak in agent workflow validation?

A delegation boundary leak in agent workflow validation occurs when command delegation prompts accidentally redefine an agent's identity, leak domain expertise, duplicate quality gates, or conflict on output contracts, causing inconsistent behavior and brittle orchestration workflows.

How do I run a delegation conflict scan across a full repository?

To run a delegation conflict scan across a full repository, you direct the AI to validate the entire skills and commands scope, which discovers Agent() calls, parses structured prompt blocks and agent contracts, and applies seven consistency checks to output an overall verdict.

Can I check for output format and quality gate duplication in my agent prompts?

Yes, you can check for output format and quality gate duplication by applying multi-dimension conflict detection that flags role re-definition, domain expertise leaks, quality gate duplication, output format conflicts, process override, scope authority conflicts, and missing contracts.

When should I run a delegation boundary validation for my orchestration changes?

You should run delegation boundary validation during workflow maintenance when adding or modifying skills, commands, or agents, and as a regression check before releasing orchestration changes to ensure commands own what and where while agents own who and how.