autonomous-auto

Automate branch-local autonomous development planning and governance for Azoth campaigns.

Updated Apr 8, 2026
One-click install
npx skills add https://github.com/yiwei79/azoth --skill autonomous-auto
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: autonomous-auto
Source: https://github.com/yiwei79/azoth/tree/main/.opencode/skills/autonomous-auto
Command: npx skills add https://github.com/yiwei79/azoth --skill autonomous-auto

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Autonomous Auto Mode enables branch-local self-development with auditable async alignment, gating, and replay controls to steer autonomous Azoth campaigns.

Core Features & Use Cases

  • Async alignment handling with vision-declaration persistence to anchor campaigns
  • Bounded replay and normal gate enforcement to ensure safe autonomous iteration
  • Operator-guided loop governor for continuing from one initiative to the next under a defined autonomy budget

Quick Start

Initialize an autonomous-auto session by presenting a concise campaign vision and securing operator approval before starting branch-local self-development.

Frequently Asked Questions about autonomous-auto

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

FAQPage Schema
How do I automate branch-local development with auditable async alignment?

Automating branch-local development requires applying autonomous campaigns within a repository, using async alignment packets and pipeline gates to govern iterations and persist decisions in run-ledger artifacts.

What is bounded replay in autonomous development pipelines?

Bounded replay is a control mechanism that ensures safe autonomous iteration by enforcing normal gate constraints, bounding the replay scope, and persisting gate state to prevent uncontrolled pipeline execution.

How do I set up an autonomous development campaign using vision declarations?

Setting up an autonomous campaign requires presenting a concise operator vision declaration, securing operator approval, and persisting the vision to anchor the branch-local self-development loop.

Can I enforce scope and pipeline gates for autonomous repository campaigns?

Yes, you can enforce scope and pipeline gates by applying autonomous campaign governance within a repository, utilizing normal gate enforcement and bounded replay to constrain autonomous iterations.

How does an operator-guided loop governor manage autonomy budgets?

An operator-guided loop governor manages autonomy budgets by steering the transition from one initiative to the next, ensuring autonomous development continues only under a defined, operator-approved budget.

Do I need frontmatter to initialize an autonomous development session?

Yes, frontmatter with a name and description is required to initialize the session, and it may optionally reference scripts, references, and assets while persisting decisions in .azoth artifacts.