Plugin finding-unknowns
Skills for finding unknowns before they get expensive, testing assumptions, examining test blindspots, and rightsizing agent context.
Cómo instalar el plugin finding-unknowns
Ejecuta ambos comandos dentro de Claude Code. El primero agrega el marketplace una vez; el segundo instala el plugin.
/plugin marketplace add Neeeophytee/finding-unknowns-skills
/plugin install finding-unknowns@finding-unknowns-skillsQué hay dentro de finding-unknowns
14 partes leídas de los archivos del propio plugin.
Skills 14
Claude lo carga cuando la tarea coincide- 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.
Usando finding-unknowns en Claude Code
Las Skills no necesitan comando. Claude las lee cuando tu solicitud coincide con lo que describen.
Actualizar, desactivar o eliminar
- Actualizar el plugin (shell)
- claude plugin update finding-unknowns@finding-unknowns-skills
- Refrescar el marketplace
- /plugin marketplace update finding-unknowns-skills
- Desactivarlo por ahora
- /plugin disable finding-unknowns@finding-unknowns-skills
- Eliminarlo
- /plugin uninstall finding-unknowns@finding-unknowns-skills
Skills en 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.
372estrellas - 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.
372estrellas - 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.
372estrellas - 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.
372estrellas - 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.
372estrellas - 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.
372estrellas - 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.
372estrellas - 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."
372estrellas - 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.
372estrellas - 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.
372estrellas - 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.
372estrellas - 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.
372estrellas - 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.
372estrellas - 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.
372estrellas
Preguntas sobre el plugin finding-unknowns
¿Cómo instalo el plugin finding-unknowns?
En Claude Code ejecuta /plugin marketplace add Neeeophytee/finding-unknowns-skills y luego /plugin install finding-unknowns@finding-unknowns-skills.
¿Qué incluye el plugin finding-unknowns?
finding-unknowns agrupa 14 skills.
¿Cómo actualizo o elimino el plugin finding-unknowns?
Actualízalo con claude plugin update finding-unknowns@finding-unknowns-skills en tu shell, o desde la pestaña Installed de /plugin. Elimínalo con /plugin uninstall finding-unknowns@finding-unknowns-skills.
¿Bajo qué licencia está el plugin finding-unknowns?
MIT, como se indica en el manifiesto del plugin.