Before You Build
Overview
Before You Build helps an AI coding workflow pause before implementation and check whether the feature, product, or tool is worth building. It focuses on product risk rather than code structure: who needs the thing, what they use today, why they would switch, how distribution works, and what evidence would make the project safer to start.
The upstream project ships a standalone skill repository and an npx installer for several coding assistants.
When to Use This Skill
- Use when a user asks an AI coding assistant to build a new app, feature, internal tool, SaaS, or side project.
- Use when the idea sounds plausible but the buyer, workflow, distribution path, or switching reason is still vague.
- Use before writing code so the assistant can turn the request into sharper assumptions, risk checks, and validation steps.
How It Works
Step 1: Identify the Build Bet
Restate the product or feature in one concrete sentence. Name the intended user, the job they are trying to finish, and the current workaround or competitor.
Step 2: Check the Main Risks
Review the idea across demand, workflow fit, willingness to switch, distribution, pricing, data access, and operational burden. Prefer specific doubts over generic brainstorming.
Step 3: Decide the Next Small Test
Suggest the smallest useful validation step before implementation. This could be a buyer conversation, landing page test, manual concierge workflow, prototype, waitlist, paid pilot, or narrow internal trial.
Step 4: Continue or Stop
If the risk is acceptable, move into implementation with the assumptions written down. If the risk is high or evidence is weak, recommend a smaller experiment instead of building the full version.
Examples
Example 1: SaaS Feature Request
User: Build a dashboard for AI trend monitoring.
Before coding, check:
- Which role needs this dashboard every week?
- What source do they use today?
- What decision changes because of the dashboard?
- Would they pay for alerts, reports, or workflow integration?
- What is the smallest manual report that proves repeat use?
Example 2: Internal Tool
User: Build an internal CRM for our small team.
Before coding, check:
- What breaks in the current spreadsheet or existing CRM?
- How many people will use it daily?
- What data must be imported or kept in sync?
- What process change is required after launch?
- Can a no-code workflow prove the need first?
Best Practices
- ✅ Ask for the user, job, current alternative, and switching reason before implementation.
- ✅ Separate product risk from engineering risk so the team does not solve the wrong problem well.
- ✅ Recommend small validation steps when the idea has weak demand evidence.
- ✅ Keep product names, numbers, and claims grounded in what the user provides.
- ❌ Do not present a generic checklist as proof that an idea is validated.
- ❌ Do not fabricate market size, revenue, competitor traction, or buyer quotes.
Limitations
- This skill does not replace customer research, legal review, financial advice, or domain expert review.
- It cannot prove demand by itself; it helps the assistant surface assumptions and choose a smaller validation step.
- If the user already has strong evidence and a clear spec, keep the review short and move into implementation.
Security & Safety Notes
- This skill is safe to run as a planning layer because it does not require credentials, external network access, or file mutation.
- If paired with an installer or repository fetch, only install from the upstream repository or npm package you trust.
Common Pitfalls
Problem: The assistant repeats the product pitch instead of challenging the assumptions.
Solution: Ask for current alternatives, switching triggers, and a validation step before code.
Problem: The review becomes too broad and blocks progress.
Solution: Pick the riskiest assumption and test only that first.
Problem: The idea is treated as a startup even when it is a small internal workflow.
Solution: Scale the risk review to the project size and only ask questions that change the build decision.
Related Skills
@saas-mvp-launcher - Use when moving from validation into MVP planning and launch execution.@ux-research-methodology - Use when the next step needs structured user research.
1---2name: before-you-build3description: Review product risk before coding by checking demand, alternatives, channels, switching costs, and failure signals.4license: MIT5---67# Before You Build89## Overview1011Before You Build helps an AI coding workflow pause before implementation and check whether the feature, product, or tool is worth building. It focuses on product risk rather than code structure: who needs the thing, what they use today, why they would switch, how distribution works, and what evidence would make the project safer to start.1213The upstream project ships a standalone skill repository and an `npx` installer for several coding assistants.1415## When to Use This Skill1617- Use when a user asks an AI coding assistant to build a new app, feature, internal tool, SaaS, or side project.18- Use when the idea sounds plausible but the buyer, workflow, distribution path, or switching reason is still vague.19- Use before writing code so the assistant can turn the request into sharper assumptions, risk checks, and validation steps.2021## How It Works2223### Step 1: Identify the Build Bet2425Restate the product or feature in one concrete sentence. Name the intended user, the job they are trying to finish, and the current workaround or competitor.2627### Step 2: Check the Main Risks2829Review the idea across demand, workflow fit, willingness to switch, distribution, pricing, data access, and operational burden. Prefer specific doubts over generic brainstorming.3031### Step 3: Decide the Next Small Test3233Suggest the smallest useful validation step before implementation. This could be a buyer conversation, landing page test, manual concierge workflow, prototype, waitlist, paid pilot, or narrow internal trial.3435### Step 4: Continue or Stop3637If the risk is acceptable, move into implementation with the assumptions written down. If the risk is high or evidence is weak, recommend a smaller experiment instead of building the full version.3839## Examples4041### Example 1: SaaS Feature Request4243```text44User: Build a dashboard for AI trend monitoring.4546Before coding, check:47- Which role needs this dashboard every week?48- What source do they use today?49- What decision changes because of the dashboard?50- Would they pay for alerts, reports, or workflow integration?51- What is the smallest manual report that proves repeat use?52```5354### Example 2: Internal Tool5556```text57User: Build an internal CRM for our small team.5859Before coding, check:60- What breaks in the current spreadsheet or existing CRM?61- How many people will use it daily?62- What data must be imported or kept in sync?63- What process change is required after launch?64- Can a no-code workflow prove the need first?65```6667## Best Practices6869- ✅ Ask for the user, job, current alternative, and switching reason before implementation.70- ✅ Separate product risk from engineering risk so the team does not solve the wrong problem well.71- ✅ Recommend small validation steps when the idea has weak demand evidence.72- ✅ Keep product names, numbers, and claims grounded in what the user provides.73- ❌ Do not present a generic checklist as proof that an idea is validated.74- ❌ Do not fabricate market size, revenue, competitor traction, or buyer quotes.7576## Limitations7778- This skill does not replace customer research, legal review, financial advice, or domain expert review.79- It cannot prove demand by itself; it helps the assistant surface assumptions and choose a smaller validation step.80- If the user already has strong evidence and a clear spec, keep the review short and move into implementation.8182## Security & Safety Notes8384- This skill is safe to run as a planning layer because it does not require credentials, external network access, or file mutation.85- If paired with an installer or repository fetch, only install from the upstream repository or npm package you trust.8687## Common Pitfalls8889- **Problem:** The assistant repeats the product pitch instead of challenging the assumptions.90 **Solution:** Ask for current alternatives, switching triggers, and a validation step before code.9192- **Problem:** The review becomes too broad and blocks progress.93 **Solution:** Pick the riskiest assumption and test only that first.9495- **Problem:** The idea is treated as a startup even when it is a small internal workflow.96 **Solution:** Scale the risk review to the project size and only ask questions that change the build decision.9798## Related Skills99100- `@saas-mvp-launcher` - Use when moving from validation into MVP planning and launch execution.101- `@ux-research-methodology` - Use when the next step needs structured user research.
bin1874