finding-unknowns プラグイン
Skills for finding unknowns before they get expensive, testing assumptions, examining test blindspots, and rightsizing agent context.
finding-unknowns プラグインのインストール方法
両方のコマンドを Claude Code 内で実行してください。最初のコマンドで marketplace を一度追加し、2 番目のコマンドでプラグインをインストールします。
/plugin marketplace add Neeeophytee/finding-unknowns-skills
/plugin install finding-unknowns@finding-unknowns-skillsfinding-unknowns の内容
プラグイン自身のファイルから読み込まれた 14 個のパーツ です。
SKILL 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 の使用方法
SKILL にコマンドは不要です。リクエストが説明と一致したときに 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 プラグインのライセンスは何ですか？
プラグインのマニフェストに記載されている MIT です。