Find and use a playbook

epismo playbook search --query "customer interview" --category sales
epismo playbook get <playbook-id>
epismo playbook version get <playbook-id> <version-id>

Review the input schema, step instructions, resource hints, and expected outputs—not only the title. A resource hint is a candidate, not proof that a resource is installed, trusted, or available.

In the web catalog, you can also browse by resource kind and then select a resource reference to see the readable playbooks that use it. GitHub and npm references are grouped by their normalized provider identity, so equivalent URL and provider-specific forms appear together.

Choose the lightest useful mode:

1. Read only: execute locally without a case.
2. Preserve results: start a lightweight case and append important records.
3. Coordinate: create tasks only for explicit ownership, approval, or handoff.

Pin the version ID when reproducibility matters. Separate improvement feedback into a suggestion.

Copy a playbook for a client

Use Copy when the client needs an independently maintained version of an existing method. Copy a readable published version to create a separate playbook with its own content and version history. The copy records its source playbook and source version so you can trace where it came from. This is similar to a GitHub fork; in Epismo, the operation is called Copy. Changes do not synchronize automatically.

1. Prepare the client team and confirm who will use and edit the method.
2. Select the owning workspace before copying. Use your workspace for a method you maintain for the client; if the client should own and maintain it, have an authorized member create the copy in their workspace. Connecting a team does not transfer ownership or billing.
3. Read the source version and check its fit and resource hints. Check that the entire copied source version is suitable for the client. If it contains internal-only material, author a new playbook from a sanitized definition instead; editing a copy later does not erase its earlier published version.
4. Copy the version with explicit initial sharing. For a client-safe source, this example creates a restricted copy shared with a team you belong to in the selected owning workspace:

epismo -w <owning-workspace> playbook copy <source-playbook-id> \
  --source-version-id <source-version-id> --team-ids <client-team-id>

If the source is client-safe but you want to review adaptations first, copy with --private instead of --team-ids, adapt it, then share the copy with the client team.

5. Use the returned copy ID for changes. Adapt inputs, tools, review criteria, and expected outputs; save a draft and publish a new version.
6. Start a case from the chosen copy version and choose case sharing explicitly. Verify that a client participant can read the playbook and work on the case.

The copy does not inherit sharing, cases, drafts, or suggestions. Its changes do not sync with the source. A reader may consult source updates only while they retain source access. Send general improvements upstream through playbook suggestions, without client-specific evidence that the source audience should not see.