@epismo

Use this workflow when an enterprise prospect or customer asks for a product capability, integration, security requirement, support model, SLA, or other commitment that may require additional company investment. The goal is to decide whether the company should make the commitment, and in what form. AI helps gather evidence and structure the decision. Sales, Product, Engineering, and customer-facing teams review the assumptions and make the final call.

A practical, batch-agnostic playbook for writing, reviewing, and defending a Y Combinator application. Suitable for idea-stage, launched, revenue-generating, and technical startups. Outcome: a clear English application supported by an evidence ledger, honest stage-appropriate metrics, founder and market insight, a founder video outline, and interview preparation. Operating principles: Lead with what the product actually does. Answer each prompt directly, then support the claim with specific, verifiable facts. Separate what has been done, observed, inferred, and planned. Show founder-specific achievements, customer understanding, execution, competitive insight, and credible potential to grow. Use plain English. Do not invent users, revenue, quotes, credentials, or results. Start with minimal context. Gather company details and evidence progressively in the steps, only when relevant. No batch deadlines or preset schedule. Exact form questions and constraints are checked when available. References live in each step's Resource Hints. The included review rubric is an editorial tool, not an official YC scoring system.

Use when someone has an Epismo account but no Playbook yet, and does not know what to write. Sets up the surface and the Epismo skill, finds the recurring work already living in their environment, filters it to the one thing a single skill cannot carry, writes it with input, output, and harness pinned so a stranger's agent can rerun it, then rehearses it against real past evidence and publishes it on the owner's go-ahead. Ends in one session with a working setup and one published, aliased Playbook — not a library plan. Quickstart — choose an install route, then say one sentence. macOS or Linux: `curl -fsSL https://epismo.ai/install.sh | sh`. Windows PowerShell: `irm https://epismo.ai/install.ps1 | iex`. npm: `npm install -g epismo`. You can also download native binaries and SHA-256 checksums directly from https://github.com/epismoai/cli/releases. Then run `epismo login`. MCP: add https://mcp.epismo.ai/ as a Streamable HTTP server with OAuth. Then prompt your agent: "Use pb:epismo/first-playbook to build my first Playbook." It will read this guidance, look at what you already do, and come back with a candidate — you only decide what to publish and to whom. Everything else is in the Steps below. Execution convention: keep intermediate materials in runtime-private scratch state, not in the user’s repository. After each meaningful step, present a concise, human-readable summary in the conversation. Create a local file only when the user explicitly asks to export one.