tx-autonomy-controls

Configure gates, guards, labels, and verification for Claude Code workflows.

6|3|Updated Jan 28, 2026
One-click install
npx skills add https://github.com/jamesaphoenix/tx --skill tx-autonomy-controls
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: tx-autonomy-controls
Source: https://github.com/jamesaphoenix/tx/tree/main/.claude/skills/tx-autonomy-controls
Command: npx skills add https://github.com/jamesaphoenix/tx --skill tx-autonomy-controls

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Bounded autonomy often requires careful orchestration of gates, guardrails, labels for context, and verification to ensure tasks finish correctly. This skill provides a structured set of commands and references to configure and manage these controls in Claude Code environments.

Core Features & Use Cases

  • Phase gates for multi-step workflows to pause and require approval before moving forward.
  • Guard rails to limit task proliferation and enforce safety constraints.
  • Label-based scoping to manage ready queues and task visibility.
  • Machine-checkable verification to define done criteria and auto-retrospectives for learning.
  • Use Case: A team deploying a multi-stage automation needs predictable gating, safe task creation, and auditable completion signals within Claude Code.

Quick Start

Configure gates, guards, labels, and verification for bounded autonomy using Claude Code.

Frequently Asked Questions about tx-autonomy-controls

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

FAQPage Schema
How do I enforce guardrails to limit task proliferation in autonomous agent workflows?

Guard rails limit task proliferation and enforce safety constraints within autonomous agent workflows. They prevent unbounded task creation and ensure operations stay within configured safety boundaries.

Can I scope task visibility using labels for bounded autonomy in Claude Code?

Machine-checkable verification defines explicit done criteria that can be programmatically validated. You use the verify command surface to set checkable completion signals for multi-step tasks.

Can I scope task visibility using labels for bounded autonomy in Claude Code?

Phase gates pause multi-step agent workflows and require approval before moving forward. You configure them using the gate command surface to enforce predictable stage transitions in Claude Code environments.

What's the best way to define machine-checkable verification criteria for agent tasks?

Auto-retrospectives generate learning records after task completion. The reflect command surface guides retrospective capture so teams can review outcomes and improve future bounded autonomy configurations.

How do I run retrospectives for completed agent workflow tasks?

No external dependencies are required. The skill provides self-contained gate, guard, label, reflect, and verify command surfaces with safety-conscious defaults and readme-backed instructions for Claude Code environments.