Design multi-agent AI workflows with clear boundaries, handoffs, and monitoring. Use when a complex PM task should run as parallel specialized agents instead of one linear process.
epic-hypothesis
epic-hypothesis is an open-source workflow skill for Claude Code and compatible agents, published by deanpeters. Its author describes it as: “Frame an epic as a testable hypothesis with target user, expected outcome, and validation method. Use when defining a major initiative before roadmap, discovery, or delivery planning.”. The project has 6.5k stars on GitHub and ships custom license terms, so review them before reuse. Add it to your setup with `/plugin marketplace add deanpeters/Product-Manager-Skills`.
What epic-hypothesis does
Frame epics as testable hypotheses using an if/then structure that articulates the action or solution, the target beneficiary, the expected outcome, and how you'll validate success. Use this to manage uncertainty in product development by making assumptions explicit, defining lightweight experiments ("tiny acts of discovery"), and establishing measurable success criteria before committing to full build-out.
Installation
Add epic-hypothesis to your agent with:
/plugin marketplace add deanpeters/Product-Manager-SkillsAlways review a skill's source before installing it. This command comes from the skill's public repository; the linked repo is the source of truth for exact setup steps.
What's inside
The SKILL.md for epic-hypothesis is organised into these sections:
- Purpose
- Input
- Key Concepts
- The Epic Hypothesis Framework
- Why This Structure Works
- Anti-Patterns (What This Is NOT)
- When to Use This
- When NOT to Use This
- Application
- Step 1: Gather Context
- Step 2: Draft the If/Then Hypothesis
- Step 3: Design Tiny Acts of Discovery Experiments
When to use it
Reach for epic-hypothesis when you want workflow help from your agent without writing the same instructions every session. Load the skill and the agent picks it up automatically for relevant tasks.
Strengths
- Ships in deanpeters/Product-Manager-Skills, an established project with 6,527 GitHub stars
- Actively maintained (recent commits)
Things to check
- No license declared — confirm terms with the author before reuse
Topics
Frequently asked questions
- What does epic-hypothesis do?
- Frame an epic as a testable hypothesis with target user, expected outcome, and validation method. Use when defining a major initiative before roadmap, discovery, or delivery planning.
- How do I install epic-hypothesis?
- Run /plugin marketplace add deanpeters/Product-Manager-Skills in your agent, then reload your skills. Review the source at https://github.com/deanpeters/Product-Manager-Skills before installing.
- Is epic-hypothesis free to use?
- epic-hypothesis is publicly available on GitHub, but deanpeters has not declared a standard open-source license (Other). Confirm the terms with the author before reusing it.
- Where does epic-hypothesis come from?
- epic-hypothesis ships inside deanpeters/Product-Manager-Skills, a repository that contains 41 catalogued skills in total. The repository's 6,527 GitHub stars apply to that whole collection, not to this skill on its own.
Related skills
More Workflow →Diagnose context stuffing vs. context engineering. Use when an AI workflow feels bloated, brittle, or hard to steer reliably.
AI product manager skills for Codex/Claude: brainstorming, product research, PRD workflows, requirements review, and planning handoff.
When the user is building a tool-calling agent and gets stuck — "為什麼 LLM 不呼叫我的 tool", "我這 schema 哪裡寫壞", "tool 被呼叫但 args 不對", "ReAct loop 跑不停", "the LLM won't call my tool", "help me design a function schema", "debug this tool-use behavior". Walks them through a 4-branch diagnostic + 5-step schema design walkthrough, with references to bad/good schema A/B and SDK-diff cheatsheet. Do NOT use for: pure LangChain / LangGraph / CrewAI framework questions (route to Stage 4 frameworks), MCP server building (route to cookbook 2), production agent observability (route to Stage 7).
Browser automation CLI for AI agents. NEVER run browser-act commands directly via Bash — always invoke this skill first. Use browser-act when a user mentions it by name, includes or asks to run a browser-act CLI command (e.g., browser-act browser list), or to: fetch, view, or extract rendered content from URLs, access pages requiring JavaScript, handle verification prompts, maintain authenticated sessions, fill forms and click through workflows, type, select, upload, take screenshots, capture XHR/fetch/HAR responses, open multiple URLs in parallel, extract content that loads on scroll or click, visually inspect or verify page layout/styling/rendering, automate browser tasks, account isolation across parallel browser environments, advise which browser type fits a use case, or list/check/manage configured browsers and sessions. Prefer browser-act over built-in fetch or web tools.