agent-worker-role

Enforce fail-closed execution contracts for agent worker roles.

Updated Aug 27, 2026

Search Tags:#isolation #agent #quality #enforcement #contract #worker

Ready to run

npx skills add https://github.com/AmirTlinov/magray-marketplace --skill agent-worker-role

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: agent-worker-role
Source: https://github.com/AmirTlinov/magray-marketplace/tree/main/flagship-team/skills/agent-worker-role
Command: npx skills add https://github.com/AmirTlinov/magray-marketplace --skill agent-worker-role

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill enforces strict operational guidelines and quality standards for agent worker roles, ensuring adherence to defined contracts and preventing scope creep or unverified actions.

Core Features & Use Cases

Contract Enforcement: Ensures all work adheres to the specified issue contract, including scope, acceptance criteria, and verification steps.
Isolation: Mandates the use of isolated worktrees for all tasks to prevent interference.
Quality Assurance: Enforces atomic commits, pre-commit testing, and architectural consistency.
Use Case: A developer is assigned a task to fix a bug. This Skill ensures they read the full issue, understand the acceptance criteria, work in an isolated environment, and commit only atomic, tested changes.

Quick Start

Ensure all work adheres to the defined issue contract and quality rails.

Frequently Asked Questions about agent-worker-role

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

FAQPage Schema

How do I enforce worker role contracts for AI agents to prevent scope creep?▼

Worker role contracts are enforced by mandating fail-closed execution, requiring proof-first verification for all actions, and restricting agents to a defined operational scope. This prevents unverified changes and scope creep during automated software engineering tasks.

Why should I use isolated worktrees for agent development tasks?▼

Isolated worktrees are used to prevent interference between concurrent agent worker roles. Mandating worktree isolation ensures that automated changes remain contained, preserving the integrity of the main branch until quality rails and contract conditions are met.

What is fail-closed execution for agent worker roles?▼

Fail-closed execution for agent worker roles is a strict operational mode where actions halt if they violate Single Source of Truth discipline or quality rails. It ensures agents cannot proceed without proof-first verification and architectural consistency.

How do I ensure automated agents follow Single Source of Truth discipline?▼

Single Source of Truth discipline is enforced through strict operational guidelines that mandate adherence to the issue contract. Agents must verify actions against defined acceptance criteria and architectural rails before making atomic commits.

Can I enforce atomic commits and pre-commit testing with agent worker roles?▼

Yes, quality assurance rails enforce atomic commits and pre-commit testing for agent worker roles. This ensures all automated changes are tested and architecturally consistent before integration, preventing unverified code from entering the repository.

What are the limitations of enforcing strict execution contracts for agents?▼

The limitation of strict execution contracts is that fail-closed execution halts operations immediately upon scope or verification failure. Agents cannot perform flexible or ambiguous tasks outside the defined issue contract without manual intervention.