atm10-change-protocol

Adapt the aoa-change-protocol workflow to ATM10 repositories with repo-relative paths and local approval notes.

4|Updated Mar 18, 2026
One-click install
npx skills add https://github.com/8Dionysus/aoa-skills --skill atm10-change-protocol
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: atm10-change-protocol
Source: https://github.com/8Dionysus/aoa-skills/tree/main/.agents/skills/atm10-change-protocol
Command: npx skills add https://github.com/8Dionysus/aoa-skills --skill atm10-change-protocol

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The skill provides a thin, repo‑specific overlay to the base aoa-change-protocol, enabling ATM10 repositories to use repo‑relative paths, commands, and local approval notes without redefining the core workflow.

Core Features & Use Cases

  • Repo‑relative adaptation: Rename files, commands, and sources of truth to match the local ATM10 repository layout.
  • Local approval integration: Embed explicit approval notes and review checklists specific to the repository.
  • Bounded workflow: Preserve the original plan → scoped change → verify → report sequence while adding local context.
  • Use Case: When a project base change protocol is correct but needs a lightweight, repository‑specific overlay for custom paths and review steps.

Quick Start

Use the atm10-change-protocol skill to generate a local change plan with repo‑relative paths and approval notes.

Frequently Asked Questions about atm10-change-protocol

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

FAQPage Schema
How do I adapt a change protocol for ATM10 repository-specific paths?

To adapt a change protocol for ATM10, apply a thin overlay that renames files, commands, and sources of truth to use repo-relative paths while preserving the core workflow. This ensures local repository layout alignment without redefining the base process.

Can I add local approval notes to an existing change protocol workflow?

Yes, you can add local approval notes by embedding explicit approval notes and review checklists specific to your repository. This integrates local review requirements directly into the bounded plan, scoped change, verify, and report sequence.

What is a repo-relative change protocol overlay and when do I need one?

A repo-relative change protocol overlay is a lightweight adaptation layer for repository-specific commands and paths. You need one when a base change protocol is correct but requires custom paths and local review steps for a specific repository.

How do I generate a local change plan with repo-relative paths and approval notes?

You generate a local change plan by applying the overlay to map sources of truth to repo-relative paths and embed local approval notes. This produces a repository-specific plan that follows the original plan, scoped change, verify, and report sequence.

Does adapting the change protocol require network connectivity and an interactive shell?

Adapting the change protocol requires access to repository files and an interactive shell, while optional network connectivity is used only for validation. This allows the workflow to function locally with optional online verification steps.

What are the limitations of using a thin overlay for workflow adaptation?

The limitation of a thin overlay for workflow adaptation is that it does not redefine the core workflow sequence. It strictly adds local context like custom paths and approval notes, meaning fundamental process changes require modifying the base protocol.