Pre-Build Risk Review
Product skill, available on Zeplik
Pre-Build Risk Review is a ready-to-run product management skill on Zeplik. Use for a pre-build risk review of demand, positioning, monetization, retention, distribution before committing to build. Ask in plain language and Zeplik applies the skill's method for you inside the conversation, on whichever AI model you prefer.
The Pre-Build Risk Review skill loads automatically when your request matches it, or you can invoke it directly by typing /before-you-build in any chat. It works with attachments, connectors, and any model that supports the task, so you get the same expert method every time without setting anything up.
What the Pre-Build Risk Review skill can do
- Run a compact pre-mortem before you start building
- Surface the single riskiest assumption behind an idea
- Recommend the smallest validation step before more work
- Flag what build scope to delay until evidence improves
Try these prompts on Zeplik
Pick a prompt to open it in the Zeplik app. If you are not signed in yet, your prompt is waiting for you the moment you do.
How the Pre-Build Risk Review skill works
/before-you-build
Run a compact pre-mortem before implementation. The goal is not to block building; it is to identify the highest-risk assumption, the smallest validation step, and the build scope that should be delayed until evidence improves.
When To Use
Use this when the user is about to build or ship:
- A new product, MVP, prototype, landing page, SaaS app, marketplace, content site, agent workflow, or internal tool
- A major feature with unclear adoption, revenue, retention, trust, or distribution impact
- A public launch asset where weak positioning could waste development or promotion effort
Skip this when the task is a narrow implementation fix, refactor, test repair, dependency update, or already-validated change with clear acceptance criteria.
Risk Checklist
Review the idea across these risks:
- Demand: Is there evidence that a specific buyer or user urgently wants this?
- Positioning: Can the target user understand what it is and why it matters in one sentence?
- Monetization: Is there a credible path to payment, budget, or strategic value?
- Retention: Is there a reason users would return after the first try?
- Trust: Does the product require credibility, data access, integrations, or behavior change that users may resist?
- Distribution: Is there a repeatable way to reach the target user?
- Feature adoption: For feature work, will the feature change user behavior or just add surface area?
If the verdict is not obvious, probe deeper on each risk: ask the user what evidence they already have (waitlist signups, interviews, search volume, existing usage data) and which risks they have not tested at all.
Output Format
Keep the response short and decision-oriented:
- Risk verdict: Low, medium, or high risk, with one sentence explaining why.
- Main assumption: The single assumption most likely to break the project.
- Evidence to find first: The smallest useful signal before building more.
- Do next: One concrete validation step or reduced build scope.
- Delay: What not to build yet.
Guidance
- Be direct about weak evidence, but avoid dismissing the user's idea.
- Prefer smaller validation steps over large research plans.
- Separate product risk from engineering difficulty.
- If the idea is already validated, say what evidence makes it lower risk and suggest the smallest implementation slice.
- If facts are missing, name the missing evidence instead of inventing market claims.
Usage
/before-you-build $ARGUMENTS
How to use the Pre-Build Risk Review skill
Sign in to Zeplik
Create a free Zeplik account or sign in. New accounts start with free credits, so you can try the Pre-Build Risk Review skill right away.
Describe your product management task
Ask in plain language, or type /before-you-build to invoke the skill directly. Zeplik recognizes the Pre-Build Risk Review skill and applies its method.
Review and refine the result
Zeplik returns a clear, structured answer. Ask follow-ups in the same chat to refine it or take the next step.
Source and credit
- Author
- wshobson
- License
- MIT
Adapted from the open-source wshobson/agents project and tuned to run natively on Zeplik. View source on GitHub.
Frequently asked questions
- What is the Pre-Build Risk Review skill?
- Pre-Build Risk Review is a ready-to-run product management skill on Zeplik. Use for a pre-build risk review of demand, positioning, monetization, retention, distribution before committing to build. Ask in plain language and Zeplik applies the skill's method for you inside the conversation, on whichever AI model you prefer.
- How do I use Pre-Build Risk Review on Zeplik?
- Sign in to Zeplik and ask in plain language, or type /before-you-build in any chat to invoke it directly. The skill applies its method and returns a result you can refine in the same conversation.
- Which AI model does the Pre-Build Risk Review skill use?
- Any model you choose. Zeplik works across every model in one chat, so the Pre-Build Risk Review skill runs on your preferred model for the task.
- Where does the Pre-Build Risk Review skill come from?
- The Pre-Build Risk Review skill is adapted from the open-source wshobson/agents project (MIT) and tuned to run natively on Zeplik. The original source is linked on this page.
- How much does the Pre-Build Risk Review skill cost?
- Using the skill is free to start. You only spend Zeplik credits when the assistant runs, and new accounts begin with free credits.
Related product skills
- Agile Product OwnerUse when writing INVEST user stories, acceptance criteria, or grooming and prioritizing a product backlog. Not for sprint ceremony planning (use sprint-planning).
- AI Product BuilderUse when building a paid product that wraps AI APIs: architecture, prompts as product, cost metering, differentiation. Not for calling the Anthropic API in code (use claude-api).
- AI Product DevelopmentIntegration, safety and cost guidance for building or hardening a production LLM feature. Not for a thin one-API SaaS (use ai-wrapper-product).
- Game-Changing FeaturesStack-ranked 10x opportunity analysis across massive/medium/small bets. Not for open-ended ideation (use product-brainstorming) or one idea into a spec (use idea-to-spec).
- Idea to SpecTurn a rough product idea into build-ready documents through staged gates: a clarifying interview in chat, then a design doc artifact, an optional UI brief, and an implementation plan. Use when the user has an app or feature idea and wants it captured, shaped, and specified before any code. Not for tasks that already have a clear spec (use plan or execplan) or for pure research questions.
- Product Brainstorm PartnerUse as a product thinking partner -- exploring a new opportunity, generating solutions to a product problem, stress-testing an idea, challenging assumptions before converging on a direction. Not for exploring a code or feature design (use brainstorming) or writing the spec (use write-spec).
More on Zeplik
Try Pre-Build Risk Review on Zeplik
Every model, one chat. Bring the Pre-Build Risk Review skill into your next conversation and let the assistant do the work.