Playbooks for people and agents
The work should outlive the agent that started it.
Playbooks preserve how great work gets done. Cases preserve just enough of the work in progress for another person—or another agent—to carry it forward.
Enterprise renewal review
How this team assesses a renewal: which sources count as evidence, and what a person has to check.
Case · Acme renewal
Work that can be resumed
Researcher
Claude CodeFinished the research and left the evidence, assumptions, and open questions in the Case.
Account exec
ChatGPTNowPicks up the thread on a different agent and keeps going, without redoing the research.
Discovery
Bring the right Playbook to the work in front of you.
Start from a way of working that already carries useful judgment, then adapt it to the situation instead of rebuilding the approach from scratch.
Enterprise renewal review
How this team assesses a renewal: which sources count as evidence, and what has to be checked by a person.
- 1Scope the renewal risk this research has to answerSkill·Renewal risk rubric
- 2Pull filings, support history, and usage into one evidence setMCP·Filings & earnings callsMCP·CRM + ticket history
- 3Separate what is verified from what is still assumedPlugin·Claim-to-source auditCLI·Exec brief builder
- 4Hand the recommendation to the account ownerTask · Review
Every Step names the Skills, MCP servers, CLIs, and plugins it expects — so a teammate's agent reproduces your run instead of improvising its own.
01 · Playbooks
Make the way of working reusable, without freezing the work.
A Playbook captures durable guidance: what to consider, which resources may help, and what a good outcome looks like. The agent runtime still decides how to execute.
Guidance, not a rigid graph
Agents can skip, combine, reorder, or extend Steps as the situation requires.
Runtime-agnostic
Use the same Playbook from Codex, Claude Code, an MCP client, or your own agent.
Auditable after the fact
What you published never changes, so you can trace which steps a past piece of work actually followed.
A learning loop
Turn lessons from real work into Suggestions, and improve the next run without rewriting history.
Continuous improvement
Let real work improve the next run.
A Playbook guides the work. A Case preserves the useful outcome. A Suggestion carries the lesson into the next run.
Find
Start from a relevant Playbook.
Improve
Propose what the next run should do better.
Run
Adapt the Steps in your agent runtime.
Share
Preserve outcomes and handoffs in a Case.
02 · Collaboration
Carry the work across people, agents, and tools.
Epismo does not copy every tool call or thought. It keeps the state collaborators actually need: the matter at hand, explicit responsibility, and durable outcomes. That is enough for the next collaborator to understand what happened and continue with confidence.
Case
One real piece of work, pinned to a Playbook Version or started ad hoc. It can be lightweight and finish without Tasks.
Task
Materialize responsibility only when someone needs to own a piece of work, review an outcome, or accept a handoff.
Record
Append outcomes, decisions, notes, and references so another collaborator can resume without replaying the entire session.
Build on what worked
Stop making every agent start from zero.
Give agents a shared way to work, preserve what matters, and let each successful Case improve the next Playbook.