Playbooks

1. Read the teams resource when workspace context matters.
2. Use epismo_playbook_resource_list when a resource kind can narrow the discovery space.
3. Find candidates with epismo_playbook_search; pass resourceKind and resourceRef together for a resource-filtered list, or use a text query instead.
4. Read the latest definition with epismo_playbook_get, which also returns the playbook's open suggestions, recent versions, and aliases in the same read (free for a public playbook, 1 credit otherwise).
5. Pin reproducible work with epismo_playbook_version_get.
6. Validate input and adapt steps into the agent runtime's plan.

A step is not a task. The agent may omit, combine, or reorder steps. Resource hints are candidates, not installation commands; check permission, trust, and credentials before use.

Use epismo_playbook_create, epismo_playbook_version_publish, and the draft tools to author playbooks. Use epismo_playbook_access_get and epismo_playbook_access_set for visibility and explicit editors. Public grants published read access only; editors can edit content. Workspace members can read and edit playbooks owned by that workspace. Any member may create a playbook owned by that workspace, or use epismo_playbook_owner_transfer to move a personally owned private playbook into it. A workspace-owned playbook can only move to that workspace's Owner or the playbook creator. An owner manager can archive a playbook or a historical version with epismo_playbook_version_archive; the latest version cannot be archived.

An authoring surface iterates through a draft instead of publishing every attempt: epismo_playbook_draft_save to save (with baseRevision, not an idempotency key), epismo_playbook_draft_get to read it back, and epismo_playbook_draft_publish or epismo_playbook_draft_discard to finish. A draft follows playbook edit access; public readers and share links cannot read it.