사용 방법
- 설치 명령을 복사하고 자신의 에이전트 환경에 설치하기 전에 소스 패키지를 확인하세요.
- 필요한 도구, 인증 정보, 지원 환경은 원본 문서에서 확인하세요.
- 입력과 원하는 산출물을 설명하고 출처와 결과를 대조하세요.
npx skills add https://github.com/wshobson/agents --skill before-you-build시작 전 확인
- 설치에는 모델 구독, API 한도, 파일 접근 권한이 포함되지 않습니다.
- 별점 수와 설치 수는 활동 지표이며 독립적인 품질·보안 검증이 아닙니다.
원본 Skill 문서
원본 저장소의 제목, 예시, 코드, 표, 링크, 이미지를 유지해 표시합니다.
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 skill when a user asks 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 skill 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, use references/risk-checklist.md for deeper questions.
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.
