Hiroki

Epismo Agent Package - Run agent workflows the community already built

by
Most AI work disappears into personal chat histories. Agent Package helps you turn it into reusable workflows and portable context that humans and agents can fork, improve, and build on. It’s not only what to prompt, but the whole actual workflow. The decisions, steps, review logic, and the entire background context. You can then reuse that knowledge across different tools (Claude Code, ChatGPT, Slack, whatever you use), share it to any discussion threads and your team. Stop starting over.

Add a comment

Replies

Best
Hiroki
Maker
📌
Hey Product Hunt 👋 I'm Hiroki, founder of Epismo. I built Agent Package because I kept getting the same problem: had an efficient workflow with my AI agent, and the session ends, and the work disappears. And I had to rebuild context from scratch next session or when switching to another tool. Sometimes I share a chat link to a teammate and I get it, it’s just tedious to read through. The real issue is that we've been sharing the wrong unit. Prompts capture what to ask, but they don't capture the decisions, the steps, logic, or the context that made the best results. Agent Package turns AI work into reusable packs: Workflow Pack captures how work runs: steps, human-agent handoffs, review logic, and acceptance checks, basically the whole operational path. Context Pack captures what the work depends on: project background, decisions, standards, assumptions, and reusable knowledge. You don't have to build it yourself. Fork a workflow from the community, whether that's market research, hiring, or product launches, then customize it anyhow. It’s simple normally (answer a few questions, or just chat with the AI using prompts that are already written) and from there, your only job is to make sure it runs well. No researching, no planning nor discussing, it saves a lot of time! You can install packs via CLI or MCP, load them into your agent, and use them across Claude, ChatGPT, Cursor, Slack, or whatever you’re already using. What I'm most excited about is the community layer. You can keep packs private, share them with your team, or publish them so others can fork and improve them. The best AI workflows shouldn't stay locked in one person's chat history. They should compound. I'd love to hear: what's the AI workflow you keep rebuilding from zero? Drop it below and I'll help turn a few into packs in this thread. Thanks for checking this out 🙏
Ben Gendler

I could see a world where teams publish context packs for their APIs so that anyone building integrations with them gets better AI results out of the box. Are you seeing that kind of use case emerge yet, or is it mostly individual teams packaging their own internal context?

Hiroki

@ben_gend Yes, definitely. I think a big opportunity is for teams to package their docs and product context in a way that works much better for agents. A lot of usage today is still internal, but this is one of the directions I’m most excited about.

Nick Kalm

This hits a real pain point, especially losing context between sessions and having to rebuild the same thinking over and over. I like the shift from just prompts to capturing the actual workflow and decisions behind the work, that part feels more useful long term. I’ve run into this a lot switching tools mid-task, so this resonates. I just upvoted it, nice work shipping this.

Hiroki

@spotch_founder Thank you!