wshobson/agents

before-you-build

Pre-build product and feature risk review for founders, product managers, and AI-assisted builders.

소스 보기

사용 방법

  1. 설치 명령을 복사하고 자신의 에이전트 환경에 설치하기 전에 소스 패키지를 확인하세요.
  2. 필요한 도구, 인증 정보, 지원 환경은 원본 문서에서 확인하세요.
  3. 입력과 원하는 산출물을 설명하고 출처와 결과를 대조하세요.
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:

  1. Risk verdict: Low, medium, or high risk, with one sentence explaining why.
  2. Main assumption: The single assumption most likely to break the project.
  3. Evidence to find first: The smallest useful signal before building more.
  4. Do next: One concrete validation step or reduced build scope.
  5. 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.

관련 작업

같은 저장소의 Skills

더 많은 Skills

모든 Skills
wshobson
커뮤니티

typescript-advanced-types

Master TypeScript's advanced type system including generics, conditional types, mapped types, template literals, and utility types for building type-safe applications. Use when implementing complex type logic, creating reusable type utilities, or ensuring compile-time type safety in TypeScript projects.

누적 설치 수
10.1만
GitHub Stars
4.3만
업데이트
11월 21일
wshobson
커뮤니티

mobile-android-design

Master Material Design 3 and Jetpack Compose patterns for building native Android apps. Use when designing Android interfaces, implementing Compose UI, or following Google's Material Design guidelines.

1시간 설치 수
2
GitHub Stars
4.3만
업데이트
11월 21일
wshobson
커뮤니티

tailwind-design-system

Build scalable design systems with Tailwind CSS v4, design tokens, component libraries, and responsive patterns. Use when creating component libraries, implementing design systems, or standardizing UI patterns.

누적 설치 수
7.5만
GitHub Stars
4.3만
업데이트
11월 18일
wshobson
커뮤니티

kpi-dashboard-design

Design effective KPI dashboards with metrics selection, visualization best practices, and real-time monitoring patterns. Use this skill when building an executive SaaS metrics dashboard tracking MRR, churn, and LTV/CAC ratios; designing an operations center with live service health and request throughput; creating a cohort retention analysis view for a product team; or debugging a dashboard where metrics contradict each other due to inconsistent calculation methodology.

1시간 설치 수
2
GitHub Stars
4.3만
업데이트
11월 18일