autonomy-protocol

Defines autonomous execution rules for executor skills after plan approval.

Updated Jun 2, 2026
One-click install
npx skills add https://github.com/lfuuu/claude-rules --skill autonomy-protocol-lfuuu
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: autonomy-protocol
Source: https://github.com/lfuuu/claude-rules/tree/main/global-skills/autonomy-protocol
Command: npx skills add https://github.com/lfuuu/claude-rules --skill autonomy-protocol-lfuuu

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Executor skills often stall mid-task by asking unnecessary confirmation questions, breaking autonomous workflows. This protocol establishes a single shared rulebook so executor skills run uninterrupted from plan approval to final report, stopping only at three defined checkpoints. ## Core Features & Use Cases - Three Stop Points: Execution halts only for plan approval, merge/commit to master, or production deploy; all other questions are forbidden. - Pre-flight Memory Check: Requires scanning project MEMORY.md for feedback and project lessons before the first non-trivial tool call. - Uncertainty Resolution Policy: Ordered decision rules resolve ambiguity without asking the user, with all decisions logged in the final report. - Self-Improvement Rule: After any error, the skill must update its own SKILL.md or LESSONS.md so the mistake cannot recur. - Use Case: A teamlead skill delegates a backend task; the backend executor imports this protocol, inherits plan approval, and runs through implementation, review iterations, and feature-branch commits without asking a single intermediate question. ## Quick Start Reference this protocol from an executor skill by adding a line stating that the autonomy-protocol applies, then let the skill execute the approved plan autonomously.

Frequently Asked Questions about autonomy-protocol

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

FAQPage Schema
How do I make an AI coding skill run autonomously without asking questions?

Import the autonomy-protocol by reference from the executor skill's SKILL.md. Once the plan is approved, the skill enters executing state and may not ask any questions outside the three stop points until the final report.

What are the three stop points in an autonomous agent workflow?

The only permitted stops are plan approval, merge or commit to master, and deploy to production. Everything else, including feature-branch commits, review iterations, and dev deploys, proceeds automatically.

How does the protocol handle ambiguity without asking the user?

It applies ordered decision rules: reuse existing project patterns, follow project conventions for new files, prefer the closest local approach, preserve backward compatibility, and retry failing tests up to three times. All decisions are logged in the final report.

When should an autonomous skill escalate back to the user?

Escalation is allowed only for unreachable secrets or access, scope changes invalidating the plan, conflicting explicit requirements, unresolvable architectural conflicts, or five consecutive failed review iterations.

How does the self-improvement rule prevent repeated agent errors?

After any error, the skill must update its own SKILL.md with a new NEVER rule or add a LESSONS.md entry recording the symptom, cause, and fix. Critical rules are wrapped in PROTECTED:RULE markers so refactors cannot remove them.