finding-unknowns 플러그인
Skills for finding unknowns before they get expensive, testing assumptions, examining test blindspots, and rightsizing agent context.
finding-unknowns 플러그인 설치 방법
두 명령을 모두 Claude Code 안에서 실행하십시오. 첫 번째는 마켓플레이스를 한 번 추가하고, 두 번째는 플러그인을 설치합니다.
/plugin marketplace add Neeeophytee/finding-unknowns-skills
/plugin install finding-unknowns@finding-unknowns-skillsfinding-unknowns 구성 요소
플러그인 파일에서 읽어온 14개의 항목입니다.
Skills 14
작업이 일치하면 Claude가 로드합니다- agent-interface-design
Design tools, scripts, and CLIs that an agent will call, so the interface teaches its own use instead of a wall of prose and examples. Use when building an MCP server or tool definition, writing an agent-facing script, or when an agent keeps misusing a tool it already has.
- assumption-test
Test a consequential technical assumption with a small, falsifiable experiment before committing to an approach. Use when a plan depends on uncertain runtime, integration, or data behavior that inspection alone cannot establish. Not for preference interviews or routine implementation.
- blindspot-pass
Surface the user's unknown unknowns before work starts. Use when the user is entering an unfamiliar codebase area, an unfamiliar domain (design, video, infra), or explicitly asks for a "blindspot pass" or to find their "unknown unknowns."
- brainstorm-prototypes
Generate several genuinely different throwaway variations (designs, approaches, drafts) for the user to react to. Use when the user can only recognize what they want by seeing it — visual design, UX flows, naming, tone — or asks to brainstorm or prototype before building.
- change-quiz
After a working session, produce a report on what changed plus a quiz the user must pass before merging. Use when the user asks "what did we actually do," wants to review a large change, or invokes a quiz before merge.
- context-audit
Audit the instructions an agent already carries — CLAUDE.md, AGENTS.md, skills, tool descriptions — for contradictions, over-constraint, and duplication, then propose a cut list. Use when an agent ignores its own instructions, when a CLAUDE.md has grown bloated, or when the user asks to audit or rightsize their agent context.
- implementation-notes
Keep a running implementation-notes.md during a build, logging every deviation from the plan and every discovered edge case. Use whenever implementing against an agreed plan or spec, especially in long autonomous sessions.
- implementation-plan
Write an implementation plan that leads with the decisions the user is most likely to change, and buries the mechanical work at the bottom. Use when planning is requested before a build, especially after brainstorming or an interview.
- interview-me
Interview the user one question at a time to resolve remaining ambiguity before implementation. Use when planning or brainstorming is done but unknowns remain, or when the user asks to be interviewed about a task or spec.
- pitch-packager
Package a finished piece of work (spec, prototype, implementation notes) into a single document that gets reviewers to understanding and approval fast. Use when the user needs buy-in, a review, or a shareable summary of what was built and why.
- progressive-disclosure
Split an oversized skill, CLAUDE.md, or spec into an entry file plus files that load only when they're needed.
- reference-hunt
Use existing source code as the specification when the user can't describe what they want in words. Use when the user points at a library, module, folder, or site and says "like this," even if it's in a different language or stack.
- regression-proof
Fix a reported bug with a regression test that demonstrably fails on the original behavior and passes after the fix. Use when implementing a bug fix or checking whether a proposed fix actually addresses a reported failure. Not a general coverage audit or new-feature workflow.
- test-blindspots
Find consequential behavior that a passing test suite does not establish, using focused exploratory checks. Use when the user asks what green tests miss or wants confidence in test coverage for a specific change. Not a general code review, routine test run, or debugging workflow for an already failing test.
Claude Code에서 finding-unknowns 사용하기
Skills는 명령어가 필요하지 않습니다. 요청이 설명과 일치하면 Claude가 이를 읽습니다.
업데이트, 비활성화 또는 삭제
- 플러그인 업데이트 (shell)
- claude plugin update finding-unknowns@finding-unknowns-skills
- marketplace 새로고침
- /plugin marketplace update finding-unknowns-skills
- 일시적으로 비활성화
- /plugin disable finding-unknowns@finding-unknowns-skills
- 삭제
- /plugin uninstall finding-unknowns@finding-unknowns-skills
finding-unknowns의 스킬
- agent-interface-designNeeeophytee/finding-unknowns-skills
Design tools, scripts, and CLIs that an agent will call, so the interface teaches its own use instead of a wall of prose and examples. Use when building an MCP server or tool definition, writing an agent-facing script, or when an agent keeps misusing a tool it already has.
372스타 - assumption-testNeeeophytee/finding-unknowns-skills
Test a consequential technical assumption with a small, falsifiable experiment before committing to an approach. Use when a plan depends on uncertain runtime, integration, or data behavior that inspection alone cannot establish. Not for preference interviews or routine implementation.
372스타 - change-quizNeeeophytee/finding-unknowns-skills
After a working session, produce a report on what changed plus a quiz the user must pass before merging. Use when the user asks "what did we actually do," wants to review a large change, or invokes a quiz before merge.
372스타 - context-auditNeeeophytee/finding-unknowns-skills
Audit the instructions an agent already carries — CLAUDE.md, AGENTS.md, skills, tool descriptions — for contradictions, over-constraint, and duplication, then propose a cut list. Use when an agent ignores its own instructions, when a CLAUDE.md has grown bloated, or when the user asks to audit or rightsize their agent context.
372스타 - progressive-disclosureNeeeophytee/finding-unknowns-skills
Split an oversized skill, CLAUDE.md, or spec into an entry file plus files that load only when they're needed.
372스타 - regression-proofNeeeophytee/finding-unknowns-skills
Fix a reported bug with a regression test that demonstrably fails on the original behavior and passes after the fix. Use when implementing a bug fix or checking whether a proposed fix actually addresses a reported failure. Not a general coverage audit or new-feature workflow.
372스타 - test-blindspotsNeeeophytee/finding-unknowns-skills
Find consequential behavior that a passing test suite does not establish, using focused exploratory checks. Use when the user asks what green tests miss or wants confidence in test coverage for a specific change. Not a general code review, routine test run, or debugging workflow for an already failing test.
372스타 - blindspot-passNeeeophytee/finding-unknowns-skills
Surface the user's unknown unknowns before work starts. Use when the user is entering an unfamiliar codebase area, an unfamiliar domain (design, video, infra), or explicitly asks for a "blindspot pass" or to find their "unknown unknowns."
372스타 - brainstorm-prototypesNeeeophytee/finding-unknowns-skills
Generate several genuinely different throwaway variations (designs, approaches, drafts) for the user to react to. Use when the user can only recognize what they want by seeing it — visual design, UX flows, naming, tone — or asks to brainstorm or prototype before building.
372스타 - implementation-notesNeeeophytee/finding-unknowns-skills
Keep a running implementation-notes.md during a build, logging every deviation from the plan and every discovered edge case. Use whenever implementing against an agreed plan or spec, especially in long autonomous sessions.
372스타 - implementation-planNeeeophytee/finding-unknowns-skills
Write an implementation plan that leads with the decisions the user is most likely to change, and buries the mechanical work at the bottom. Use when planning is requested before a build, especially after brainstorming or an interview.
372스타 - interview-meNeeeophytee/finding-unknowns-skills
Interview the user one question at a time to resolve remaining ambiguity before implementation. Use when planning or brainstorming is done but unknowns remain, or when the user asks to be interviewed about a task or spec.
372스타 - pitch-packagerNeeeophytee/finding-unknowns-skills
Package a finished piece of work (spec, prototype, implementation notes) into a single document that gets reviewers to understanding and approval fast. Use when the user needs buy-in, a review, or a shareable summary of what was built and why.
372스타 - reference-huntNeeeophytee/finding-unknowns-skills
Use existing source code as the specification when the user can't describe what they want in words. Use when the user points at a library, module, folder, or site and says "like this," even if it's in a different language or stack.
372스타
finding-unknowns 플러그인 질문
finding-unknowns 플러그인은 어떻게 설치하나요?
Claude Code에서 /plugin marketplace add Neeeophytee/finding-unknowns-skills를 실행한 다음 /plugin install finding-unknowns@finding-unknowns-skills을 실행하십시오.
finding-unknowns 플러그인에는 무엇이 포함되나요?
finding-unknowns은(는) 14개 스킬을(를) 묶습니다.
finding-unknowns 플러그인을 어떻게 업데이트하거나 삭제하나요?
shell에서 claude plugin update finding-unknowns@finding-unknowns-skills를 사용하여 업데이트하거나 /plugin의 Installed 탭에서 수행하세요. 삭제하려면 /plugin uninstall finding-unknowns@finding-unknowns-skills을 사용하세요.
finding-unknowns 플러그인의 라이선스는 무엇인가요?
플러그인 manifest에 명시된 대로 MIT입니다.