{"id":"before-you-build","name":"before-you-build","summary":"創業者、プロダクトマネージャー、AI支援ビルダー向けの事前構築製品および機能リスクレビュー。ユーザーがランディングページ、MVP、SaaS製品、社内ツール、エージェントワークフロー、または主要機能を構築しようとし、需要、ポジショニング、収益化、定着率、TRなどを確認する必要がある場合にこのスキルを活用してください。","body":"# Before You Build\n\nRun 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.\n\n## When To Use\n\nUse this skill when a user asks to build or ship:\n\n- A new product, MVP, prototype, landing page, SaaS app, marketplace, content site, agent workflow, or internal tool\n- A major feature with unclear adoption, revenue, retention, trust, or distribution impact\n- A public launch asset where weak positioning could waste development or promotion effort\n\nSkip this skill when the task is a narrow implementation fix, refactor, test repair, dependency update, or already-validated change with clear acceptance criteria.\n\n## Risk Checklist\n\nReview the idea across these risks:\n\n- **Demand:** Is there evidence that a specific buyer or user urgently wants this?\n- **Positioning:** Can the target user understand what it is and why it matters in one sentence?\n- **Monetization:** Is there a credible path to payment, budget, or strategic value?\n- **Retention:** Is there a reason users would return after the first try?\n- **Trust:** Does the product require credibility, data access, integrations, or behavior change that users may resist?\n- **Distribution:** Is there a repeatable way to reach the target user?\n- **Feature adoption:** For feature work, will the feature change user behavior or just add surface area?\n\nIf the verdict is not obvious, use `references/risk-checklist.md` for deeper questions.\n\n## Output Format\n\nKeep the response short and decision-oriented:\n\n1. **Risk verdict:** Low, medium, or high risk, with one sentence explaining why.\n2. **Main assumption:** The single assumption most likely to break the project.\n3. **Evidence to find first:** The smallest useful signal before building more.\n4. **Do next:** One concrete validation step or reduced build scope.\n5. **Delay:** What not to build yet.\n\n## Guidance\n\n- Be direct about weak evidence, but avoid dismissing the user's idea.\n- Prefer smaller validation steps over large research plans.\n- Separate product risk from engineering difficulty.\n- If the idea is already validated, say what evidence makes it lower risk and suggest the smallest implementation slice.\n- If facts are missing, name the missing evidence instead of inventing market claims.","author":"@wshobson","ownerProfile":null,"authorContacts":null,"sourceUrl":"https://github.com/wshobson/agents/tree/main/plugins/before-you-build/skills/before-you-build","license":"MIT","category":"coding","lang":"en","tokens":489,"stars":0,"calls30d":2,"claimed":false,"visibility":"public","origin":"crawler","version":"0.1.0","createdAt":"2026-08-22","updatedAt":"2026-08-22","files":[{"path":"references/risk-checklist.md","size":1611,"sha256":"7cb5c4a2c20252f6d084ecac6d05727ccadf5c80513e34d04bb740a0636130fe"}],"requires":{"mcp":[],"tools":[]},"safety":{"flags":[],"scannedAt":"2026-08-22","hasScripts":false,"networkEndpoints":[]}}