AGENT SKILL

playbook-composition

Use when adopting, authoring, routing, assessing, or updating repository concern-based playbooks.

License 许可
MIT
最近更新
2026-10-08
Stars
★ 0
Forks
0

01 前言 Front Matter

name
playbook-composition
license
MIT
metadata
{ "owner": "Harley Bartles", "status": "active", "use_when": [ "the human asks to adopt or assess the playbook-composition standard.", "the repository subscribes to the standard and reusable concern playbooks or their routes are changing." ], "source-id": "playbook-composition", "source-path": "skills/playbook-composition/SKILL.md", "do_not_use_when": [ "the document is a lifecycle-stage procedure owned by a runbook.", "the repository has no subscription and no explicit adoption or assessment request for this standard." ], "provenance-name": "Playbook Composition first-party skill", "source-category": "first_party" }
description
Use when adopting, authoring, routing, assessing, or updating repository concern-based playbooks.

02 资源文件 8

03 SKILL.md 正文

Playbook Composition

Use the playbook composition standard when a repository explicitly adopts or asks to assess playbook-composition. Inspect its pinned subscription and certification. A playbook can stand alone; runbooks and doctrine/contracts are optional standards.

AOM offers optional editable testing, security, and code-review concern guides, plus a checker starter. A repository may select any subset, author its own playbooks, adapt or replace these examples, or omit them all. Adoption is an agent-led repository change; the repository owns selected files and its compliance chain. The checker accepts selected document and route-source paths, then checks file/link integrity only, including inline and reference-style local Markdown links and images; code examples do not count as links. It does not determine whether a guide is a cross-stage concern, useful, or effectively routed through non-Markdown mechanisms.

04 同仓库更多 Skills