before-you-build · onewave-ai — Claude Code skill for idea validation
The before-you-build skill identifies the main risk in an idea and suggests a small test before implementation starts. Use it to assess a product, feature, MVP, agent, or automation.
MIT 130 installs ★ 440 updated 2026-10-20
npx skills add OneWave-AI/claude-skills --skill before-you-build -a claude-codeWhat before-you-build does
Before development, the skill restates the idea, picks the one or two risks that matter most, and proposes a step to reduce uncertainty. It checks factors such as demand, willingness to pay, access to users, fit with existing workflows, trust, timing, and scope. The response gives a risk verdict and a direction: build, narrow the build, validate first, or hold off.
Suggested tests can include asking users about past attempts, seeking a commitment before writing software, or delivering the outcome manually once. If the idea lacks enough detail, the skill asks a clarifying question. For learning or portfolio work, it focuses on scope and the learning goal rather than startup criteria. It deliberately avoids stack, architecture, tool, and code advice, so it is not meant for requests that already concern implementation alone.
What it helps with
- identify the biggest product risk before coding
- test demand before committing to an MVP
- check whether a feature blocks payment or retention
- shrink a project to the proof needed now
- set a clear learning goal for a portfolio project
Example prompts for the agent
- Assess this appointment-booking product idea before I build it. Which risk should I test first?
- For this feature in an existing product, check whether it blocks payment and suggest a small validation step.
- This is a portfolio project. Help me narrow the scope and define what I should learn.
How to install before-you-build
1Skills CLI (Vercel)
npx skills add OneWave-AI/claude-skills --skill before-you-build -a claude-code2Manually: put the files in place
~/.claude/skills/before-you-build/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/before-you-build/
1Skills CLI (Vercel)
npx skills add OneWave-AI/claude-skills --skill before-you-build -a codex2Manually: put the files in place
.agents/skills/before-you-build/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add OneWave-AI/claude-skills --skill before-you-build -a cursor2Manually: put the files in place
.cursor/skills/before-you-build/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install OneWave-AI/claude-skills before-you-build2Manually: put the files in place
.github/skills/before-you-build/SKILL.md1Skills CLI (Vercel)
npx skills add OneWave-AI/claude-skills --skill before-you-build -a gemini-cli2Platform CLI
gemini skills install https://github.com/OneWave-AI/claude-skills --path before-you-buildManually: put the files in place
.devin/skills/before-you-build/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add OneWave-AI/claude-skills --skill before-you-build -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about before-you-build
How do I install before-you-build in Claude Code?
Run npx skills add OneWave-AI/claude-skills --skill before-you-build -a claude-code. The skill file is at ~/.claude/skills/before-you-build/SKILL.md.
What does before-you-build do?
It reviews an idea before implementation, identifies its main risk, and recommends a small way to test it. The response also gives a risk verdict and a suggested next move.
Can before-you-build recommend a tech stack?
No. It focuses on product assumptions before implementation and avoids recommending stacks, architectures, tools, or code.
Source text
SKILL.md · MIT
--- name: before-you-build description: Use before starting a product, feature, MVP, agent, automation, or integration build to identify the main pre-build risk and choose the smallest validation step. Trigger when the user asks whether to build, scope, validate, prioritize, or sanity-check an idea before implementation. --- # Before You Build Use this skill as a short pre-build risk gate. The goal is to stop implementation from starting before the riskiest product assumption is clear. Stay implementation-agnostic: do not recommend stacks, architectures, tools, or code. ## Core Behavior When invoked: 1. Restate the idea in one sentence. 2. Identify the dominant pre-build risk. 3. Give a short risk verdict. 4. Recommend the smallest validation step that can reduce uncertainty before building. Keep the response short unless the user explicitly asks for a deeper review. ## Seven Risk Dimensions Check the idea through these dimensions: - Demand risk: Do enough people already feel this problem strongly? - Buyer risk: Is there a clear person or team with reason to pay or commit? - Distribution risk: Is there a believable path to reaching those people? - Workflow risk: Does the idea fit how users already behave, decide, or work? - Timing risk: Is this urgent now, or only interesting in theory? - Trust risk: Does the product require data, access, behavior change, or credibility users may not grant? - Scope risk: Is the proposed build larger than the proof needed right now? Pick the one or two risks that matter most. Do not turn every review into a long checklist. ## Output Format Use this format: ```markdown ## Before You Build Idea: - [One-sentence restatement.] Risk verdict: - [Low / Medium / High risk] because [one concrete reason]. Main risk: - [The dominant risk dimension and why it matters.] Smallest validation step: - [One specific action the user can take before building.] Build guidance: - [Build now / Build smaller / Validate first / Do not build yet.] ``` ## Validation Step Rules The smallest validation step should be specific and low-cost. Prefer steps like: - Talk to five target users who already tried to solve the problem. - Ask for payment, pre-order, letter of intent, or manual commitment before building software. - Run a landing page, waitlist, outbound message, or concierge test around one narrow promise. - Manually deliver the outcome once before automating it. - Test whether the missing feature blocks payment, retention, activation, or only completeness. - Find one repeated channel that can reach the target users before expanding scope. Avoid steps like: - Build the MVP first. - Add more features to see what happens. - Choose a tech stack. - Design the architecture. - Write code. - Create a broad product roadmap. ## Special Cases If the idea is too vague, ask one clarification question: ```text Who is this for, what painful situation are they in, and how do they solve it today? ``` If the user is asking about a feature for an existing product, focus on whether the feature is a real blocker for payment, retention, activation, trust, or delivery. If the user says the project is for learning, portfolio, or fun, do not judge it by startup standards. Focus on keeping scope small and making the learning outcome clear. If the decision to build is already made and the user only wants implementation help, do not use this skill. ## Style Be direct, skeptical, and useful. Do not be dismissive. The point is not to kill ideas; the point is to make the next build decision harder to fool yourself about.
© OneWave-AI · MIT · OneWave-AI/claude-skills
Similar skills
All skills for Notes, tasks and projects →before-you-build by other authors comes first.