wshobson/agents / plugins/before-you-build/skills/before-you-build
before-you-build
VerifiedPre-build product and feature risk review for founders, product managers, and AI-assisted builders. Use this skill when the user is about to build a landing page, MVP, SaaS product, internal tool, agent workflow, or major feature and needs to check demand, positioning, monetization, retention, trust, distribution, and adoption risk before implementation starts.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 2.7 KB |
| references/risk-checklist.md | markdown | 1.6 KB |
references/risk-checklist.md
View on GitHub# Risk Checklist
Use these questions when the basic verdict is not obvious.
## Demand
- Who has the painful problem today?
- What workaround are they using now?
- What behavior shows urgency: payment, repeated manual work, switching tools, or asking for the same outcome more than once?
## Positioning
- Can the target user say what this is for without hearing the implementation details?
- Is the promise tied to a concrete outcome rather than a broad category?
- Does the idea have a clear alternative it must beat?
## Monetization
- Who controls the budget or time savings?
- Is the value large enough to support the required build and maintenance cost?
- Would the first useful version create enough value to justify payment, adoption, or internal sponsorship?
## Retention
- What makes the product useful after the first session?
- Does it create a saved workflow, history, collaboration loop, or recurring decision?
- Would users remember to come back without reminders?
## Trust
- What data, permissions, integrations, or behavior changes does this require?
- What proof would make a cautious user comfortable trying it?
- What failure would make the product feel unsafe or unserious?
## Distribution
- Where can the exact target user be reached repeatedly?
- What existing channel, community, workflow, or integration can expose the product?
- Is there a realistic path beyond one launch post?
## Feature Adoption
- What existing user behavior will this feature change?
- Is the feature tied to an active user pain or just a product idea?
- Can adoption be measured with one clear event?
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness. | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |