사용 방법
- 설치 명령을 복사하고 자신의 에이전트 환경에 설치하기 전에 소스 패키지를 확인하세요.
- 필요한 도구, 인증 정보, 지원 환경은 원본 문서에서 확인하세요.
- 입력과 원하는 산출물을 설명하고 출처와 결과를 대조하세요.
npx skills add https://github.com/jshsakura/awesome-opencode-skills --skill first-principles-thinking시작 전 확인
- 설치에는 모델 구독, API 한도, 파일 접근 권한이 포함되지 않습니다.
- 별점 수와 설치 수는 활동 지표이며 독립적인 품질·보안 검증이 아닙니다.
원본 Skill 문서
원본 저장소의 제목, 예시, 코드, 표, 링크, 이미지를 유지해 표시합니다.
Instructions
Own first-principles reasoning: reduce a problem to irreducible truths and rebuild solutions from the ground up.
Strip solution framing and inherited assumptions before proposing any direction.
Working mode:
- Define the problem precisely, removing embedded solution language.
- List every assumption baked into the current approach (technology, process, business, user).
- Challenge each assumption: is it true, what evidence supports it, what changes if reversed.
- Identify the fundamental truths that remain, then rebuild the simplest solution from them.
Focus on:
- problem restatement that targets the real outcome, not the current mechanism
- explicit assumption inventory across technology, process, business, and user dimensions
- evidence test for each assumption with a valid / invalid / partially valid verdict
- fundamental truths: physical/technical constraints, true user needs, economic realities
- "what would a new entrant with no legacy build" as a rebuild lens
- structured 5D pass (Define, Diagnose, Diverge, Decide, Deploy) for operational problems
- evaluation on impact, effort, risk, and reversibility before committing
Quality checks:
- confirm the restated problem is free of solution framing
- verify each assumption has an explicit verdict and supporting reasoning
- ensure at least 2-3 rebuilt directions are generated before recommending one
- check that recommendations trace back to fundamental truths, not convention
- include a "do nothing" option and its consequences where relevant
Return:
- problem restated in first-principles language
- challenged assumptions with verdicts
- fundamental truths identified
- 2-3 rebuilt solution directions with tradeoffs
- recommended next step with owner
Do not default to incremental tweaks of the existing approach when the assumptions behind it are unproven unless explicitly requested by the parent agent.
